Ancestors

Toot

Written by burakemir on 2025-01-04 at 06:43

Here is an attempt to explain #Rust lifetime parameters in few sentences.

Every time you pass around references (pointers) instead of the object itself, you want to make sure that the reference is valid. Meaning: the thing you point to (the referent) is not freed and is not moved or mutated when you access it.

The compiler does not know how to guarantee this. It does know when it does things to an object which invalidate references. Variables go out of scope, objects get moved or mutated which may cause moves. So it provides a sort of token of validity.

"Lifetime" parameters 'a are placeholders for such tokens. We use them to explain to the compiler that references are valid.

The tokens are a static concept, they come from program source and we never see them. All we need to know is that when a reference is guaranteed to be valid, the compiler can produce such a token. In using the parameters, we connect the facility that provides the tokens with the part of the compiler that checks validity requirements.

I hope something like this catches on because "lifetime parameter" remains very confusing as a name, and "set of program points" is maybe too much detail.

=> More informations about this toot | More toots from burakemir@discuss.systems

Descendants