That's a very nicecly written article.
Just a quick question, isn't point 8 outdated (misconctption: “Rust borrow checker does adanced liftime analysis”) due to the introduction NLL (no lexical lifetime) in Rust 2018?
this post was submitted on 03 Sep 2023
37 points (97.4% liked)
Rust
6117 readers
10 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 2 years ago
MODERATORS
There are still obvious things the BC cannot get. For example:
struct Foo;
impl Foo {
fn num(&mut self) -> usize { 0 }
fn index(&mut self, _i: usize) { }
}
let foo = Foo;
foo.index(foo.num()); //error
This looks like a pretty easy fix that the compiler could do by extracting the argument to a temp variable to improve the syntax of the language.
Note that when you change num to take &self instead, this works out (you also need to mark foo as mutable, of course).
It's a toy example. In that case, the solution is to assign the expression to a variable to compute its result upfront.