Common Rust Lifetime Misconceptions (2020) (github.com)

submitted 1 year ago by lysdexic@programming.dev to c/rust@programming.dev

5 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] robinm@programming.dev 5 points 1 year ago

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?

[-] hairyballs@programming.dev 1 points 1 year ago* (last edited 1 year ago)

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

[-] KillTheMule@programming.dev 1 points 1 year ago* (last edited 1 year ago)

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

[-] hairyballs@programming.dev 1 points 1 year ago

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

load more comments (1 replies)

this post was submitted on 03 Sep 2023

37 points (97.4% liked)

Rust

5999 readers

18 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

kahnclusions@programming.dev

torcherist@programming.dev