Ownership Highlights Summary

Every highlight bullet from the 12 pages in this section, gathered on one page and grouped by the page it came from.

The Rust Ownership Model

• Every value has exactly one owner at a time; that owner decides when it is cleaned up
• Assignment moves non-Copy values by default; only marked types duplicate on assignment
• The borrow checker allows many readers or one writer to a value, never both at once
• Lifetimes are not a runtime concept - they are the compiler's bookkeeping for reference validity

Ownership Basics

• Each value has exactly one owner responsible for cleanup
• Moves transfer ownership; the source binding becomes invalid
• Drop runs automatically when the owner goes out of scope

Move Semantics & Copy

• Copy types duplicate bits on assignment; moves invalidate the source
• Clone is explicit deep duplication for heap data
• Generics use Copy bounds when values must remain valid after assignment

Borrowing & References

• Many &T OR one &mut T to the same data at a time
• References must not outlive the data they borrow
• Reborrowing narrows mutable access temporarily

The Borrow Checker

• The borrow checker proves memory safety at compile time
• Errors describe conflicting loans - read the spans carefully
• Refactoring data flow usually fixes issues faster than fighting the compiler

Lifetimes Explained

• Lifetimes label how long references remain valid
• They are compile-time annotations, not runtime counters
• Output references cannot outlive their inputs unless tied to 'static

Lifetime Annotations

• Annotate when elision cannot connect input and output references
• Struct lifetimes mean the struct cannot outlive borrowed fields
• 'a: 'b means 'a lives at least as long as 'b

Lifetime Elision

• Elision applies default lifetime relationships in common fn signatures
• Each elided input gets its own lifetime; output ties to inputs
• Methods often assign &self lifetime to returned references

Non-Lexical Lifetimes & Reborrows

• NLL ends borrows at last use, not necessarily at end of scope
• Reborrowing creates shorter sub-loans from an existing loan
• Two-phase borrows help some method call patterns compile

'static & Bounds

• 'static means the reference can live for the entire program
• String literals are &'static str stored in the binary
• Lifetime bounds on generics constrain how long type parameters may borrow

Fighting the Borrow Checker

• Restructure data flow before reaching for interior mutability
• Split structs, push values out, or clone at API boundaries
• Indices and arenas replace many self-referential designs

Ownership Best Practices

• Take &str, &[T], &Path for read-only inputs
• Return owned values unless zero-copy is a measured win
• Use &mut self methods for in-place updates
• Minimize lifetime parameters on public structs
• Derive Copy only for small, stack-only types
• Do not hold locks across .await