Dangling reference prevention in Rust - Step-by-Step Execution

Concept Flow - Dangling reference prevention

Create variable with data

↓

Create reference to variable

↓

Use reference safely

↓

Variable goes out of scope

↓

Reference invalidated automatically

↓

Compiler prevents dangling reference

This flow shows how Rust creates a reference to data, uses it safely, and prevents the reference from outliving the data to avoid dangling references.

Execution Sample

Rust

fn main() {
    let s = String::from("hello");
    let r = &s;
    println!("{}", r);
}

This code creates a string, makes a reference to it, and prints the referenced value safely.

Execution Table

Step	Action	Variable States	Reference Validity	Output
1	Create variable s with "hello"	s = "hello"	No references yet
2	Create reference r to s	s = "hello", r -> s	r valid, points to s
3	Print value via r	s = "hello", r -> s	r valid	hello
4	End of main scope, s dropped	s dropped	r invalidated automatically

💡 Program ends, compiler ensures r never outlives s, preventing dangling reference

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
s	uninitialized	"hello"	"hello"	"hello"	dropped
r	uninitialized	uninitialized	reference to s	reference to s	invalidated

Key Moments - 3 Insights

Why can't we use the reference r after s is dropped?

Because in step 4, s is dropped and r would point to invalid memory. Rust's compiler prevents this to avoid dangling references, as shown in the exit note.

What happens if we try to create a reference to a variable that does not live long enough?

Rust's compiler will give an error and refuse to compile the code, ensuring references never outlive the data they point to, preventing dangling references as seen between steps 2 and 4.

Is the reference r a copy of s's data?

No, r is a pointer to s's data, not a copy. This is why r must not outlive s, as shown in the variable_tracker and execution_table.

Visual Quiz - 3 Questions

Look at the execution table, what is the state of r at step 3?

A r is invalid because s is dropped

B r is uninitialized

C r is a valid reference pointing to s

D r holds a copy of s's data

💡 Hint

Check the 'Reference Validity' column at step 3 in the execution_table

At which step does the variable s get dropped, invalidating r?

A Step 4

B Step 3

C Step 2

D Never dropped

💡 Hint

Look at the 'Variable States' column in the execution_table for when s is dropped

If we tried to use r after step 4, what would Rust do?

A Allow it without error

B Give a compile-time error preventing dangling reference

C Crash at runtime

D Copy s's data to r automatically

💡 Hint

Refer to the exit_note and key_moments about Rust's prevention of dangling references

Concept Snapshot

Dangling reference prevention in Rust:
- References (&) must not outlive the data they point to.
- Rust compiler checks lifetimes at compile time.
- Variables dropped at scope end invalidate references.
- Prevents unsafe memory access automatically.
- Use references safely within variable lifetimes.

Full Transcript

This example shows how Rust prevents dangling references by ensuring references do not outlive the data they point to. We create a string variable s, then a reference r to s. We use r to print the string safely. When the main function ends, s is dropped and r is invalidated automatically. Rust's compiler enforces these rules at compile time, preventing any dangling references and unsafe memory access.

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