RS-LIFE0002 · evidence
This page continues RS-LIFE0002 directly from its source docstring. Read its implementation.
Evidence
Section titled “Evidence”Each finding names the declaration that demands the pin and the line it is written on, and states how many pins the module holds in total so a reader can see what share demands. The repair is a choice, since owning the data and keeping the pin honestly are both real answers. The value is the number of demanding pins.
Exceptions
Section titled “Exceptions”A T: 'static bound is not counted, because a bound says what a type may not borrow rather
than pinning any particular value, and a thread, a task, or a trait object often requires one.
A return position is not counted, because promising a longer lifetime than required takes
nothing away from a caller. A field that genuinely holds a compile-time table, and an interner
that leaks on purpose, both demand honestly, and a project excludes those rather than owning
data it never frees.
References
Section titled “References”- Cites “The Rust Reference”, static lifetime. Open reference
- Cites “Rust by Example”, the static lifetime and its two meanings. Open reference
- Cites “corrode”, do not worry about lifetimes. Open reference