Using unwrap and expect in Rust - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the unwrap() method do in Rust?

unwrap() extracts the value inside an Option or Result if it exists. If the value is None or Err, it causes the program to panic and stop.

beginner

How is expect() different from unwrap()?

expect() works like unwrap() but lets you provide a custom error message that shows when the program panics.

intermediate

When should you prefer expect() over unwrap()?

Use expect() when you want to give a clear message about why the program failed. This helps debugging by explaining what went wrong.

beginner

What happens if you call unwrap() on a None value?

The program will panic and stop running, showing a default error message about calling unwrap() on a None value.

beginner

Show a simple Rust example using expect() with a custom error message.

<pre>let text = Some("hello");
let value = text.expect("Expected a string but found None");
println!("Value: {}", value);</pre>

What does unwrap() do when called on None?

A Panics and stops the program

B Returns a default value

C Returns <code>None</code>

D Ignores the error and continues

unwrap() panics if called on None because there is no value to extract.

Which method lets you add a custom panic message?

A expect()

B unwrap()

C unwrap_or()

D unwrap_or_else()

expect() lets you provide a custom message that shows when the program panics.

Why is it better to use expect() instead of unwrap() in some cases?

A Because <code>unwrap()</code> is slower

B Because <code>expect()</code> never panics

C Because <code>expect()</code> provides a clear error message

D Because <code>unwrap()</code> returns an Option

expect() helps debugging by showing a clear message when something goes wrong.

What type of Rust values can you call unwrap() on?

A Only <code>Option</code>

B <code>Option</code> and <code>Result</code>

C Any type

D Only <code>Result</code>

unwrap() works on both Option and Result types.

What is the risk of using unwrap() in your code?

A It can cause silent errors

B It changes the data type

C It slows down the program

D It can cause the program to panic unexpectedly

Using unwrap() can cause your program to panic and stop if the value is missing or an error.

Explain in your own words what unwrap() and expect() do in Rust and when you might use each.

Think about how they handle missing or error values.

Describe a situation where using expect() would be better than unwrap().

Consider how error messages help you find bugs.

Practice

1. What does the unwrap() method do when called on an Option in Rust?

easy

A. Always returns Some without checking the value.

B. Returns None if the value is missing without panicking.

C. Returns the value inside if Some, or panics if None.

D. Converts the Option into a Result type.

Solution

1. Step 1: Understand unwrap behavior on Option

   The unwrap() method extracts the value inside an Option if it is Some.

2. Step 2: What happens if Option is None

   If the Option is None, unwrap() causes the program to panic and stop.

3. Final Answer:

   Returns the value inside if Some, or panics if None. -> Option C

4. Quick Check:

   unwrap() panics on None = C [OK]

Hint: unwrap() panics on None, returns value on Some [OK]

Common Mistakes:

• Thinking unwrap returns None instead of panicking
• Confusing unwrap with expect
• Assuming unwrap converts Option to Result

2. Which of the following is the correct syntax to use expect on an Option with a custom error message?

easy

A. option.unwrap("Custom error message")

B. option.expect("Custom error message")

C. option.expect_error("Custom error message")

D. option.unwrap_or("Custom error message")

Solution

1. Step 1: Recall expect syntax

   The expect method is called on an Option or Result with a string argument for the error message.

2. Step 2: Identify correct method and argument

   The correct syntax is option.expect("Custom error message"). Other options are invalid method names or wrong usage.

3. Final Answer:

   option.expect("Custom error message") -> Option B

4. Quick Check:

   expect() takes a string message = A [OK]

Hint: expect() needs a string message inside parentheses [OK]

Common Mistakes:

• Using unwrap with a message argument
• Using non-existent methods like expect_error
• Confusing unwrap_or with expect

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

let value: Option<i32> = Some(10);
println!("{}", value.unwrap());

medium

A. None

B. Compilation error

C. panic at unwrap called on None

D. 10

Solution

1. Step 1: Check Option value

   The variable value is Some(10), so it contains the integer 10.

2. Step 2: unwrap() extracts the value

   Calling unwrap() on Some(10) returns 10 without panicking.

3. Final Answer:

   10 -> Option D

4. Quick Check:

   unwrap() on Some(10) = 10 [OK]

Hint: unwrap() returns inner value if Some, else panics [OK]

Common Mistakes:

• Expecting None as output
• Thinking unwrap returns Option again
• Assuming code panics on Some

4. Identify the error in this Rust code snippet:

let value: Option<i32> = None;
println!("{}", value.unwrap());

medium

A. Runtime panic because unwrap called on None

B. Compilation error due to unwrap on None

C. unwrap returns 0 by default

D. No error, prints None

Solution

1. Step 1: Analyze Option value

   The variable value is None, meaning it has no value inside.

2. Step 2: unwrap() behavior on None

   Calling unwrap() on None causes a runtime panic and stops the program.

3. Final Answer:

   Runtime panic because unwrap called on None -> Option A

4. Quick Check:

   unwrap() panics on None = D [OK]

Hint: unwrap() panics at runtime if Option is None [OK]

Common Mistakes:

• Thinking unwrap returns None safely
• Expecting compilation error instead of panic
• Assuming unwrap returns default value

5. You want to safely get a value from an Option<String> but provide a clear error message if it's None. Which code snippet correctly uses expect for this?

hard

A. let name = option_name.expect("Name was missing!");

B. let name = option_name.unwrap_or("Name was missing!");

C. let name = option_name.unwrap("Name was missing!");

D. let name = option_name.expect_error("Name was missing!");

Solution

1. Step 1: Understand expect usage

   The expect method extracts the value or panics with the provided custom message if None.

2. Step 2: Check each option

   let name = option_name.expect("Name was missing!"); correctly uses expect with a string message. let name = option_name.unwrap_or("Name was missing!"); uses unwrap_or which returns a default value, not an error. The remaining options use invalid syntax.

3. Final Answer:

   let name = option_name.expect("Name was missing!"); -> Option A

4. Quick Check:

   expect() with message = A [OK]

Hint: Use expect("message") to add custom panic messages [OK]

Common Mistakes:

• Using unwrap_or instead of expect for error message
• Passing message to unwrap (not allowed)
• Using non-existent expect_error method