Why borrowing is required in Rust - The Real Reasons

The Big Idea

What if you could share your data safely without giving it away or making copies?

The Scenario

Imagine you have a book that you want to share with your friends. If you give the book to one friend, you can't use it yourself until they return it. But if you want to let many friends read it without losing your copy, how do you do that?

The Problem

Without borrowing, you would have to make many copies of the book for each friend. This wastes time and space. Also, if you want to change the book, you must update every copy, which is slow and error-prone.

The Solution

Borrowing lets you lend the book temporarily without giving it away. Your friends can read or use the book, but you keep ownership. This way, you avoid making copies and keep control, making your program safe and efficient.

Before vs After

✗ Before

let s = String::from("hello");
let s2 = s; // s is moved, no longer usable
println!("{}", s); // error!

✓ After

let s = String::from("hello");
let s2 = &s; // borrow s
println!("{}", s); // works fine

What It Enables

Borrowing allows safe sharing of data without unnecessary copying or losing ownership, making programs faster and more reliable.

Real Life Example

When multiple parts of a program need to read the same data, borrowing lets them do so without conflicts or crashes, like friends reading the same book without fighting over it.

Key Takeaways

Borrowing prevents data duplication and ownership loss.

It enables safe, temporary access to data.

Borrowing helps write efficient and error-free Rust programs.

Practice

1. Why does Rust require borrowing when accessing data instead of always transferring ownership?

easy

A. To allow multiple parts of code to read data without copying it

B. To make the code run slower for safety

C. To force programmers to write more code

D. To prevent any data from being changed

Solution

1. Step 1: Understand ownership and borrowing

   Ownership means one variable controls the data. Borrowing lets others use data without owning it.

2. Step 2: Why borrowing is useful

   Borrowing allows multiple parts of code to read data safely without making copies or moving ownership.

3. Final Answer:

   To allow multiple parts of code to read data without copying it -> Option A

4. Quick Check:

   Borrowing = safe shared access [OK]

Hint: Borrowing means sharing data without moving ownership [OK]

Common Mistakes:

• Thinking borrowing slows down code
• Believing borrowing prevents all data changes
• Confusing borrowing with copying data

2. Which of the following is the correct syntax to borrow a variable immutably in Rust?

easy

A. let x = ref value;

B. let x = &value;

C. let &x = value;

D. let mut x = &mut value;

Solution

1. Step 1: Identify borrowing syntax

   In Rust, borrowing immutably uses the ampersand before the variable: &value.

2. Step 2: Match correct syntax

   The correct way to bind a reference is let x = &value;. Other options are invalid or mean something else.

3. Final Answer:

   let x = &value; -> Option B

4. Quick Check:

   Immutable borrow = &value [OK]

Hint: Use & before variable to borrow immutably [OK]

Common Mistakes:

• Using let x = ref value; invalid syntax
• Confusing &x with &value
• Using mutable borrow (&mut) for immutable access

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

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

medium

A. hello and hello

B. Compilation error due to multiple mutable borrows

C. hello and error

D. Runtime error

Solution

1. Step 1: Analyze borrowing in code

   Two immutable references r1 and r2 borrow s simultaneously, which is allowed.

2. Step 2: Check output of println!

   Both references print the string "hello", so output is "hello and hello".

3. Final Answer:

   hello and hello -> Option A

4. Quick Check:

   Multiple immutable borrows print values [OK]

Hint: Multiple immutable borrows allowed, prints values [OK]

Common Mistakes:

• Thinking multiple immutable borrows cause errors
• Confusing mutable and immutable borrow rules
• Expecting runtime errors for borrowing

4. Identify the error in this Rust code and why borrowing is required:

fn main() {
    let mut s = String::from("hello");
    let r1 = &s;
    let r2 = &mut s;
    println!("{} and {}", r1, r2);
}

medium

A. No error, code runs fine

B. Cannot borrow `s` as immutable because it is mutable

C. Cannot borrow `s` as mutable because it is already borrowed as immutable

D. Cannot print two variables in println!

Solution

1. Step 1: Check borrowing rules

   Rust forbids mutable borrow while immutable borrow exists to prevent data races.

2. Step 2: Identify error cause

   Here, r1 immutably borrows s, then r2 tries mutable borrow, causing compile error.

3. Final Answer:

   Cannot borrow `s` as mutable because it is already borrowed as immutable -> Option C

4. Quick Check:

   Mutable borrow blocked by existing immutable borrow [OK]

Hint: Mutable borrow blocked if immutable borrow exists [OK]

Common Mistakes:

• Thinking mutable borrow is allowed with immutable borrow
• Ignoring borrow checker errors
• Assuming println! causes error

5. You want to write a function that changes a string passed to it without taking ownership. Which borrowing type should you use and why?

hard

A. Immutable borrow (&) because it allows reading the string safely

B. Copy the string inside the function to modify it

C. Ownership transfer because borrowing is not needed for modification

D. Mutable borrow (&mut) because it allows modifying the string without ownership

Solution

1. Step 1: Understand function parameter needs

   To modify data inside a function without taking ownership, you must borrow it mutably.

2. Step 2: Choose correct borrow type

   Mutable borrow &mut allows changing the original data safely without moving ownership.

3. Final Answer:

   Mutable borrow (&mut) because it allows modifying the string without ownership -> Option D

4. Quick Check:

   Modify data = use &mut borrow [OK]

Hint: Use &mut to change data without ownership transfer [OK]

Common Mistakes:

• Using immutable borrow when modification is needed
• Transferring ownership unnecessarily
• Copying data instead of borrowing