Why smart pointers are needed in Rust - See It in Action

Why smart pointers are needed

📖 Scenario: Imagine you are managing a small library of books. Each book can be borrowed by readers, and you want to keep track of who has borrowed which book. You also want to make sure that when a book is no longer borrowed, it is safely returned to the library without losing track of it.

🎯 Goal: You will create a simple Rust program that shows why smart pointers are needed to manage memory safely and automatically. You will start by creating a basic data structure, then add a smart pointer to manage ownership, and finally see how Rust helps avoid common mistakes.

📋 What You'll Learn

Create a struct called Book with a title field

Create a variable called book that holds a Book instance

Use Box smart pointer to store the Book

Print the book title using the smart pointer

💡 Why This Matters

🌍 Real World

Smart pointers are used in real programs to manage memory safely without manual cleanup. This helps prevent bugs like memory leaks or crashes.

💼 Career

Understanding smart pointers is essential for Rust developers to write safe and efficient code, especially in systems programming and applications requiring precise memory control.

1

Create a struct and a book variable

Create a struct called Book with a field title of type String. Then create a variable called book that holds a Book with the title "The Rust Book".

Rust

# Define the Book struct
// Your code here

// Create a variable book with title "The Rust Book"
// Your code here

Hint

Use struct to define Book. Use String::from to create the title.

2

Use a Box smart pointer to store the book

Create a variable called book_box that stores the book inside a Box smart pointer.

Rust

struct Book {
    title: String,
}

fn main() {
    let book = Book {
        title: String::from("The Rust Book"),
    };
    // Create book_box using Box::new(book)
    // Your code here
}

Hint

Use Box::new(book) to create a smart pointer.

3

Access the book title through the smart pointer

Use a println! macro to print the book title by accessing book_box.title.

Rust

struct Book {
    title: String,
}

fn main() {
    let book = Book {
        title: String::from("The Rust Book"),
    };
    let book_box = Box::new(book);
    // Print the title using book_box
    // Your code here
}

Hint

Use println! to show the title inside the box.

4

See why smart pointers help manage memory

Add a comment explaining that Box helps store data on the heap and manages memory safely without manual freeing.

Rust

struct Book {
    title: String,
}

fn main() {
    let book = Book {
        title: String::from("The Rust Book"),
    };
    let book_box = Box::new(book);
    println!("Book title: {}", book_box.title);
    // Add a comment about why Box is useful
    // Your code here
}

Hint

Write a simple comment explaining the benefit of Box.

Practice

1. Why do we need smart pointers in Rust instead of just using regular references?

easy

A. To manage memory automatically and prevent dangling pointers

B. To make the code run faster by skipping safety checks

C. To allow variables to change type during runtime

D. To avoid writing functions in Rust

Solution

1. Step 1: Understand Rust's memory safety goals

   Rust aims to prevent memory bugs like dangling pointers and double frees by managing ownership strictly.

2. Step 2: Role of smart pointers

   Smart pointers automatically manage memory and ensure safe access, preventing common bugs that raw references can't handle alone.

3. Final Answer:

   To manage memory automatically and prevent dangling pointers -> Option A

4. Quick Check:

   Memory safety = Automatic management [OK]

Hint: Smart pointers help manage memory safely and automatically [OK]

Common Mistakes:

• Thinking smart pointers make code faster by skipping checks
• Believing smart pointers change variable types
• Confusing smart pointers with general Rust syntax

2. Which of the following is the correct way to create a smart pointer using Box in Rust?

easy

A. let b = new Box(5);

B. let b = box 5;

C. let b = Box(5);

D. let b = Box::new(5);

Solution

1. Step 1: Recall Box syntax

   In Rust, Box::new(value) creates a new Box smart pointer holding the value.

2. Step 2: Check each option

   let b = Box::new(5); uses correct syntax. let b = box 5; is outdated syntax. Options C and D are invalid in Rust.

3. Final Answer:

   let b = Box::new(5); -> Option D

4. Quick Check:

   Box creation = Box::new(value) [OK]

Hint: Use Box::new(value) to create a Box smart pointer [OK]

Common Mistakes:

• Using outdated 'box' keyword
• Trying to call Box like a function
• Using 'new Box' which is invalid

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

use std::rc::Rc;

let a = Rc::new(10);
let b = Rc::clone(&a);
println!("{}", Rc::strong_count(&a));

medium

A. 2

B. 10

C. 1

D. Compilation error

Solution

1. Step 1: Understand Rc and cloning

   Rc is a smart pointer for shared ownership. Cloning an Rc increases the reference count.

2. Step 2: Count references after cloning

   After cloning a, there are two owners: a and b. So, Rc::strong_count(&a) returns 2.

3. Final Answer:

   2 -> Option A

4. Quick Check:

   Rc clones increase count = 2 [OK]

Hint: Rc::clone increases count; check strong_count for number [OK]

Common Mistakes:

• Thinking Rc::clone copies data instead of pointer
• Expecting count to be 1 after clone
• Confusing Rc with Box

4. Identify the error in this Rust code using smart pointers:

use std::rc::Rc;

let a = Rc::new(5);
let mut b = a;
b = Rc::new(10);

medium

A. Cannot assign to immutable variable 'a'

B. No error, code runs fine

C. Rc pointers cannot be reassigned

D. Cannot make 'b' mutable after initialization

Solution

1. Step 1: Check variable mutability

   Variable b is declared mut, so reassignment is allowed.

2. Step 2: Analyze ownership move

   let mut b = a; moves the Rc from a to b. a becomes invalid but is not used afterward.

3. Step 3: Verify reassignment

   b = Rc::new(10); creates a new Rc and reassigns it to the mutable b. The old Rc is dropped safely.

4. Final Answer:

   No error, code runs fine -> Option B

5. Quick Check:

   Ownership move but no further use of a [OK]

Hint: Check mutability and ownership moves carefully [OK]

Common Mistakes:

• Confusing move with borrow
• Assuming Rc pointers are immutable
• Ignoring variable mutability

5. You want multiple parts of your program to share ownership of a value and also mutate it safely. Which smart pointer combination should you use in Rust?

hard

A. Box<T>

B. Rc<T>

C. Rc

D. Arc<T>

Solution

1. Step 1: Understand ownership and mutability needs

   Multiple owners require Rc (Reference Counted) smart pointer to share ownership.

2. Step 2: Add interior mutability

   Since Rc alone does not allow mutation, wrapping the value in RefCell enables safe mutable access at runtime.

3. Step 3: Combine for shared mutable ownership

   The combination Rc<RefCell<T>> allows multiple owners with controlled mutability.

4. Final Answer:

   Rc<RefCell<T>> -> Option C

5. Quick Check:

   Shared ownership + mutability = Rc [OK]

Hint: Use Rc with RefCell for shared mutable ownership [OK]

Common Mistakes:

• Using Box which does not allow shared ownership
• Using Rc alone which is immutable
• Confusing Arc with Rc for single-threaded code