Dangling reference prevention in Rust - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a dangling reference in Rust?

A dangling reference is a pointer or reference that points to memory that has been freed or is no longer valid. Rust prevents this to ensure memory safety.

beginner

How does Rust prevent dangling references?

Rust uses its ownership system and borrowing rules, enforced at compile time, to ensure references never outlive the data they point to.

intermediate

What role does the borrow checker play in preventing dangling references?

The borrow checker verifies that all references are valid and do not outlive the data they borrow, preventing dangling references before the program runs.

intermediate

Why can't Rust allow a reference to a local variable to escape its function?

Because the local variable is dropped when the function ends, any reference to it would become invalid, causing a dangling reference. Rust forbids this at compile time.

intermediate

What is a lifetime in Rust and how does it help prevent dangling references?

A lifetime is a compile-time annotation that tells Rust how long a reference is valid. It helps the compiler ensure references do not outlive the data they point to, preventing dangling references.

What does Rust's borrow checker ensure?

A Variables can be used after they are dropped

B References do not outlive the data they point to

C Memory is manually freed by the programmer

D References can point to any memory location

Rust's borrow checker ensures references are always valid and do not outlive their data, preventing dangling references.

Why is a reference to a local variable invalid after the function returns?

A The local variable is dropped and memory is freed

B The reference automatically copies the data

C Rust allows references to live forever

D The reference becomes a mutable borrow

Local variables are dropped when the function ends, so references to them become invalid, which Rust prevents.

Which Rust feature helps specify how long references are valid?

A Traits

B Macros

C Enums

D Lifetimes

Lifetimes tell Rust the scope of validity for references, helping prevent dangling references.

What happens if you try to return a reference to a local variable in Rust?

A Compile error due to lifetime violation

B Program runs normally

C Reference is automatically cloned

D Reference becomes static

Rust's compiler will reject code that returns a reference to a local variable because it would be a dangling reference.

Which of these is NOT a way Rust prevents dangling references?

A Ownership rules

B Borrowing rules

C Garbage collection

D Lifetimes

Rust does not use garbage collection; it relies on ownership, borrowing, and lifetimes to prevent dangling references.

Explain how Rust's ownership and borrowing system prevents dangling references.

Think about how Rust tracks who owns data and how references borrow it safely.

Describe what a lifetime is in Rust and why it is important for preventing dangling references.

Lifetimes tell Rust how long references can be used.

Practice

1. What does Rust do to prevent dangling references?

easy

A. It automatically deletes all references after use.

B. It enforces borrowing rules and lifetimes to ensure references are valid.

C. It uses garbage collection to clean up unused references.

D. It allows references to point to any memory without checks.

Solution

1. Step 1: Understand what dangling references are

   Dangling references point to data that no longer exists, causing bugs.

2. Step 2: Identify Rust's prevention method

   Rust uses borrowing rules and lifetimes to ensure references are always valid while used.

3. Final Answer:

   It enforces borrowing rules and lifetimes to ensure references are valid. -> Option B

4. Quick Check:

   Dangling reference prevention = borrowing rules + lifetimes [OK]

Hint: Remember: Rust checks lifetimes to avoid invalid references [OK]

Common Mistakes:

• Thinking Rust uses garbage collection
• Believing references are deleted automatically
• Assuming Rust allows unchecked references

2. Which of the following Rust code snippets correctly prevents a dangling reference?

easy

A. let r;
{
let x = 5;
r = &x;
}
println!("{}", r);

B. let r = &5;
println!("{}", r);

C. let r = &x;
let x = 5;
println!("{}", r);

D. let x = 5;
let r = &x;
println!("{}", r);

Solution

1. Step 1: Analyze each snippet for lifetime validity

   let r; { let x = 5; r = &x; } println!("{}", r); creates a reference to x inside a block, but x is dropped before use, causing dangling reference. let r = &5; println!("{}", r); creates a reference to a temporary value 5, which is dropped while borrowed, causing compile error. let x = 5; let r = &x; println!("{}", r); creates x and r in the same scope, so r is valid. let r = &x; let x = 5; println!("{}", r); tries to reference x before x is declared, so x not in scope, compile error.

2. Step 2: Identify the snippet that correctly prevents dangling references

   let x = 5; let r = &x; println!("{}", r); is the correct example where the reference r points to x which lives long enough for r to be used safely.

3. Final Answer:

   let x = 5; let r = &x; println!("{}", r); -> Option D

4. Quick Check:

   Reference lifetime valid in same scope = let x = 5; let r = &x; println!("{}", r); [OK]

Hint: Keep referenced data alive in the same scope as the reference [OK]

Common Mistakes:

• Referencing variables that go out of scope too early
• Declaring references before the data they point to
• Assuming temporary values always live long enough

3. What will be the output of this Rust code?

fn main() {
    let r;
    {
        let x = 10;
        r = &x;
    }
    println!("{}", r);
}

medium

A. Compilation error due to dangling reference

B. 10

C. Undefined behavior at runtime

D. 0

Solution

1. Step 1: Understand variable lifetimes in the code

   Variable x is declared inside the inner block and dropped when the block ends. Reference r points to x but is used outside the block.

2. Step 2: Identify Rust's behavior on this code

   Rust's compiler detects that r would be a dangling reference because x does not live long enough. It will produce a compilation error.

3. Final Answer:

   Compilation error due to dangling reference -> Option A

4. Quick Check:

   Dangling reference causes compile error in Rust [OK]

Hint: References must not outlive the data they point to [OK]

Common Mistakes:

• Expecting code to run and print 10
• Thinking Rust allows unsafe dangling references
• Confusing runtime errors with compile-time errors

4. Identify the error in this Rust code and how to fix it:

fn get_ref() -> &i32 {
    let x = 42;
    &x
}

medium

A. Error: missing lifetime annotation. Fix by adding explicit lifetime.

B. No error, code is correct.

C. Error: returning reference to local variable. Fix by returning the value instead.

D. Error: x is not mutable. Fix by declaring x as mutable.

Solution

1. Step 1: Analyze the function's return type and variable scope

   The function returns a reference to an integer, but x is a local variable that is dropped when the function ends.

2. Step 2: Identify the problem and fix

   Returning a reference to a local variable causes a dangling reference. The fix is to return the value itself (i32) instead of a reference.

3. Final Answer:

   Error: returning reference to local variable. Fix by returning the value instead. -> Option C

4. Quick Check:

   Don't return references to local variables [OK]

Hint: Never return references to variables that go out of scope [OK]

Common Mistakes:

• Adding lifetimes without fixing the root cause
• Making variables mutable unnecessarily
• Ignoring that local variables are dropped after function ends

5. You want to return a reference to a string slice from a function without causing dangling references. Which approach is correct?

fn first_word(s: &String) -> &str {
    // ???
}

hard

A. Return a slice of s using lifetimes: &s[..1]

B. Create a new String inside the function and return a reference to it

C. Return a reference to a local string variable inside the function

D. Return the whole String by value instead of a reference

Solution

1. Step 1: Understand the input and output lifetimes

   The function takes a reference to a String and returns a string slice (&str) referencing part of that String.

2. Step 2: Choose the safe way to return a slice without dangling references

   Returning a slice of the input String (&s[..1]) is safe because the slice's lifetime is tied to the input reference's lifetime.

3. Final Answer:

   Return a slice of s using lifetimes: &s[..1] -> Option A

4. Quick Check:

   Return slices tied to input lifetimes to avoid dangling references [OK]

Hint: Return slices of input references, not local variables [OK]

Common Mistakes:

• Returning references to local variables
• Creating new owned Strings and returning references to them
• Ignoring lifetime relationships between input and output