rustlings/exercises/16_lifetimes
2024-04-11 02:51:02 +02:00
..
lifetimes1.rs Remove "I AM NOT DONE" and the verify mode and add AppState 2024-04-11 02:51:02 +02:00
lifetimes2.rs Remove "I AM NOT DONE" and the verify mode and add AppState 2024-04-11 02:51:02 +02:00
lifetimes3.rs Remove "I AM NOT DONE" and the verify mode and add AppState 2024-04-11 02:51:02 +02:00
README.md Update Exercises Directory Names to Reflect Order 2023-10-16 07:37:12 -04:00

Lifetimes

Lifetimes tell the compiler how to check whether references live long enough to be valid in any given situation. For example lifetimes say "make sure parameter 'a' lives as long as parameter 'b' so that the return value is valid".

They are only necessary on borrows, i.e. references, since copied parameters or moves are owned in their scope and cannot be referenced outside. Lifetimes mean that calling code of e.g. functions can be checked to make sure their arguments are valid. Lifetimes are restrictive of their callers.

If you'd like to learn more about lifetime annotations, the lifetimekata project has a similar style of exercises to Rustlings, but is all about learning to write lifetime annotations.

Further information