robinm comments on Common Rust Lifetime Misconceptions (2020)

[–] robinm@programming.dev 5 points 2 years ago (1 child)

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?

permalink

fedilink

source

hideshow 2 child comments

[–] hairyballs@programming.dev 1 point 2 years ago* (2 children)

There are still obvious things the BC cannot get. For example:

struct Foo;

impl Foo {
    fn num(&amp;mut self) -> usize { 0 }
    fn index(&amp;mut self, _i: usize) { }
}

let foo = Foo;
foo.index(foo.num()); //error

permalink

fedilink

source

parent

hideshow 4 child comments

[–] sirdorius@programming.dev 2 points 2 years ago*

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.

permalink

fedilink

source

parent

[–] KillTheMule@programming.dev 1 point 2 years ago* (1 child)

Note that when you change num to take &self instead, this works out (you also need to mark foo as mutable, of course).

permalink

fedilink

source

parent

hideshow 2 child comments

[–] hairyballs@programming.dev 1 point 2 years ago

It's a toy example. In that case, the solution is to assign the expression to a variable to compute its result upfront.

permalink

fedilink

source

parent

lemmy:	0.19.20
mlmym (mschae):	26.3.4