Why Rust is used - See It in Action

Why Rust is Used

📖 Scenario: Imagine you are a software developer who wants to build a fast and safe program. You have heard about Rust, a programming language that helps you do this well.

🎯 Goal: You will create a simple Rust program that shows why Rust is used by printing key reasons. This will help you understand Rust's benefits in a clear way.

📋 What You'll Learn

Create a list of reasons why Rust is used

Add a variable to count the number of reasons

Use a loop to print each reason with its number

Print the total number of reasons at the end

💡 Why This Matters

🌍 Real World

Rust is used in real-world projects where safety and speed are important, like web browsers, game engines, and operating systems.

💼 Career

Knowing why Rust is used helps you explain its benefits in job interviews and understand when to choose Rust for software development.

1

Create a list of reasons why Rust is used

Create a variable called reasons that is a vector containing these exact strings: "Memory safety without garbage collection", "Fast performance", "Concurrency without data races", "Great tooling and compiler errors".

Rust

# Create a vector called reasons with the given strings
# Your code here

Hint

Use let reasons = vec!["string1", "string2", ...]; to create the list.

2

Add a variable to count the number of reasons

Add a variable called count that stores the length of the reasons vector using reasons.len().

Rust

fn main() {
    let reasons = vec![
        "Memory safety without garbage collection",
        "Fast performance",
        "Concurrency without data races",
        "Great tooling and compiler errors",
    ];
    // Create a variable count to store the length of reasons
    // Your code here
}

Hint

Use let count = reasons.len(); to get the number of items.

3

Use a loop to print each reason with its number

Use a for loop with variables i and reason to iterate over reasons.iter().enumerate(). Inside the loop, print each reason with its number starting from 1 using println!("{}. {}", i + 1, reason);.

Rust

fn main() {
    let reasons = vec![
        "Memory safety without garbage collection",
        "Fast performance",
        "Concurrency without data races",
        "Great tooling and compiler errors",
    ];
    let count = reasons.len();
    // Use a for loop with i and reason to print each reason with its number
    // Your code here
}

Hint

Use for (i, reason) in reasons.iter().enumerate() { ... } and print with println!("{}. {}", i + 1, reason);.

4

Print the total number of reasons at the end

After the loop, print the total number of reasons using println!("Total reasons: {}", count);.

Rust

fn main() {
    let reasons = vec![
        "Memory safety without garbage collection",
        "Fast performance",
        "Concurrency without data races",
        "Great tooling and compiler errors",
    ];
    let count = reasons.len();
    for (i, reason) in reasons.iter().enumerate() {
        println!("{}. {}", i + 1, reason);
    }
    // Print the total number of reasons
    // Your code here
}

Hint

Use println!("Total reasons: {}", count); to show the total.

Practice

1. Why do many programmers choose Rust for their projects?

easy

A. Because Rust is mainly used for web design

B. Because Rust helps write fast and reliable programs

C. Because Rust does not support memory safety

D. Because Rust is only for beginners

Solution

1. Step 1: Understand Rust's main benefits

   Rust is known for speed and reliability in programming.

2. Step 2: Compare options with Rust's features

   Only Because Rust helps write fast and reliable programs correctly states Rust helps write fast and reliable programs.

3. Final Answer:

   Because Rust helps write fast and reliable programs -> Option B

4. Quick Check:

   Rust = fast and reliable [OK]

Hint: Remember Rust focuses on speed and safety [OK]

Common Mistakes:

• Thinking Rust is only for web design
• Believing Rust ignores memory safety
• Assuming Rust is just for beginners

2. Which of the following is the correct way to describe Rust's memory management?

easy

A. Rust uses garbage collection to manage memory automatically

B. Rust requires manual memory management like C

C. Rust does not manage memory at all

D. Rust uses ownership rules to manage memory safely without garbage collection

Solution

1. Step 1: Recall Rust's memory management approach

   Rust uses ownership and borrowing rules to manage memory safely without garbage collection.

2. Step 2: Match options with Rust's method

   Rust uses ownership rules to manage memory safely without garbage collection correctly describes Rust's ownership system; others are incorrect.

3. Final Answer:

   Rust uses ownership rules to manage memory safely without garbage collection -> Option D

4. Quick Check:

   Ownership system = Rust memory management [OK]

Hint: Rust uses ownership, not garbage collection [OK]

Common Mistakes:

• Confusing Rust with languages that use garbage collection
• Thinking Rust requires manual memory freeing
• Believing Rust ignores memory management

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

fn main() {
    let x = vec![1, 2, 3];
    let y = x;
    println!("{:?}", x);
    println!("{:?}", y);
}

medium

A. Compilation error due to use of moved value

B. [1, 2, 3]

C. [] (empty vector)

D. Runtime error

Solution

1. Step 1: Understand ownership move in Rust

   Assigning x to y moves ownership of the vector from x to y.

2. Step 2: Check usage of x after move

   Using x after move causes a compile-time error because x no longer owns the data.

3. Final Answer:

   Compilation error due to use of moved value -> Option A

4. Quick Check:

   Using moved value = compile error [OK]

Hint: Using moved variable causes compile error [OK]

Common Mistakes:

• Expecting x to still hold the vector after move
• Thinking Rust allows use after move
• Confusing runtime error with compile error

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

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

medium

A. Missing semicolon after println! macro

B. String::from is incorrect syntax; fix by using str literal

C. Cannot have mutable and immutable references at the same time; fix by removing one reference

D. No error; code runs fine

Solution

1. Step 1: Understand Rust's borrowing rules

   Rust forbids having mutable and immutable references to the same data at the same time.

2. Step 2: Identify the conflict in code

   r1 is immutable reference, r2 is mutable reference; this causes a compile error.

3. Final Answer:

   Cannot have mutable and immutable references at the same time; fix by removing one reference -> Option C

4. Quick Check:

   Mutable + immutable refs = error [OK]

Hint: Mutable and immutable refs cannot coexist [OK]

Common Mistakes:

• Ignoring Rust's borrowing rules
• Thinking String::from is wrong syntax
• Assuming code compiles without error

5. You want to write a Rust program that safely shares read-only access to data across multiple parts of your program without copying. Which Rust feature helps achieve this best?

hard

A. Using the Rc<T> type for shared ownership with immutable references

B. Using global variables without ownership

C. Using unsafe pointers to bypass ownership rules

D. Using multiple mutable references (&mut) to the data

Solution

1. Step 1: Understand the need for shared read-only access

   Multiple parts need to read data without copying or mutating it.

2. Step 2: Identify Rust feature for shared ownership

   Rc<T> allows multiple owners with immutable references safely.

3. Step 3: Eliminate unsafe or incorrect options

   Mutable references cannot be multiple; unsafe pointers bypass safety; globals lack ownership control.

4. Final Answer:

   Using the Rc<T> type for shared ownership with immutable references -> Option A

5. Quick Check:

   Shared ownership = Rc<T> [OK]

Hint: Use Rc<T> for shared read-only ownership [OK]

Common Mistakes:

• Trying multiple mutable references
• Using unsafe pointers unnecessarily
• Relying on global variables without ownership