Bird
Raised Fist0
Rustprogramming~30 mins

Lifetimes in structs in Rust - Mini Project: Build & Apply

Choose your learning style10 modes available
Lifetimes in structs
📖 Scenario: Imagine you are creating a program that stores a short message and its author. You want to make sure the message and author data live long enough while your program uses them.
🎯 Goal: You will build a Rust struct that holds references to a message and its author using lifetimes. This will help you understand how to use lifetimes in structs to avoid errors.
📋 What You'll Learn
Create a struct called Message with lifetime parameter 'a
Add two fields to Message: content and author, both string slices with lifetime 'a
Create a variable msg_content with the exact string "Hello, Rust!"
Create a variable msg_author with the exact string "Alice"
Create an instance of Message called message using msg_content and msg_author
Print the message content and author using println!
💡 Why This Matters
🌍 Real World
Lifetimes in structs are important when you want to store references safely without copying data, such as in text processing or configuration management.
💼 Career
Understanding lifetimes helps you write safe and efficient Rust code, a valuable skill for systems programming, embedded development, and performance-critical applications.
Progress0 / 4 steps
1
Create the Message struct with lifetime
Create a struct called Message with a lifetime parameter 'a. It should have two fields: content and author, both of type &'a str.
Rust
Hint

Use struct Message<'a> to declare the lifetime. Both fields should be &'a str.

2
Create message content and author variables
Create two variables: msg_content with the string "Hello, Rust!" and msg_author with the string "Alice".
Rust
Hint

Use let msg_content = "Hello, Rust!"; and let msg_author = "Alice";.

3
Create a Message instance using the variables
Create a variable called message of type Message using msg_content for content and msg_author for author.
Rust
Hint

Use let message = Message { content: msg_content, author: msg_author };.

4
Print the message content and author
Use println! to print the message in the format: "Message: Hello, Rust! by Alice" using message.content and message.author.
Rust
Hint

Use println!("Message: {} by {}", message.content, message.author); to print.

Practice

(1/5)
1. What is the main purpose of using lifetimes in Rust structs?
easy
A. To make structs mutable by default
B. To increase the speed of the program
C. To allow structs to own data permanently
D. To tell Rust how long references inside the struct are valid

Solution

  1. Step 1: Understand what lifetimes represent

    Lifetimes describe how long references are valid to prevent invalid memory access.
  2. Step 2: Connect lifetimes to structs

    In structs, lifetimes tell Rust how long the references inside the struct remain valid.
  3. Final Answer:

    To tell Rust how long references inside the struct are valid -> Option D
  4. Quick Check:

    Lifetimes = reference validity [OK]
Hint: Lifetimes track reference validity duration in structs [OK]
Common Mistakes:
  • Thinking lifetimes control program speed
  • Confusing ownership with lifetimes
  • Assuming lifetimes make structs mutable
2. Which of the following is the correct syntax to declare a struct with a lifetime parameter named 'a'?
easy
A. struct Example { data: &str<'a> }
B. struct Example<'a> { data: &'a str }
C. struct Example { data: &'a str }
D. struct Example<'a> { data: &str'a }

Solution

  1. Step 1: Recall lifetime syntax in structs

    Lifetime parameters are declared after the struct name with angle brackets, e.g., 'a.
  2. Step 2: Match correct placement of lifetime

    The lifetime must be declared as 'a after struct name and used before the reference type.
  3. Final Answer:

    struct Example<'a> { data: &'a str } -> Option B
  4. Quick Check:

    Lifetime syntax = struct Name<'a> { field: &'a Type } [OK]
Hint: Lifetime goes after struct name and before reference type [OK]
Common Mistakes:
  • Placing lifetime after &str instead of before
  • Omitting lifetime parameter after struct name
  • Using incorrect lifetime syntax like &str<'a>
3. What will be the output of this Rust code?
struct Holder<'a> {
    value: &'a i32,
}

fn main() {
    let x = 10;
    let h = Holder { value: &x };
    println!("{}", h.value);
}
medium
A. 10
B. Compilation error due to missing lifetime
C. Runtime error: dangling reference
D. 0

Solution

  1. Step 1: Analyze struct and lifetime usage

    The struct Holder has a lifetime 'a for its reference field. The reference &x is valid inside main.
  2. Step 2: Check code execution

    Variable x is 10, h.value references x, so printing h.value outputs 10.
  3. Final Answer:

    10 -> Option A
  4. Quick Check:

    Reference points to 10, so output = 10 [OK]
Hint: Valid lifetime means reference prints correct value [OK]
Common Mistakes:
  • Assuming compilation error without lifetime annotation
  • Expecting runtime error for valid reference
  • Confusing output with zero or default
4. Identify the error in this Rust code:
struct Container<'a> {
    data: &'a str,
}

fn main() {
    let c;
    {
        let s = String::from("hello");
        c = Container { data: &s };
    }
    println!("{}", c.data);
}
medium
A. Error: 's' does not live long enough for 'c'
B. Error: Missing lifetime parameter in struct
C. Error: Cannot print &str directly
D. No error, code runs fine

Solution

  1. Step 1: Understand variable lifetimes

    Variable 's' is created inside inner block and dropped at block end.
  2. Step 2: Analyze reference validity

    Container 'c' holds reference to 's', but 's' is dropped before 'c' is used, causing invalid reference.
  3. Final Answer:

    Error: 's' does not live long enough for 'c' -> Option A
  4. Quick Check:

    Reference lifetime shorter than struct usage = error [OK]
Hint: Check if referenced data outlives struct instance [OK]
Common Mistakes:
  • Ignoring inner block scope of 's'
  • Thinking missing lifetime parameter causes error here
  • Assuming printing &str causes error
5. You want to create a struct that holds two string slices with different lifetimes. Which is the correct way to declare it?
hard
A. struct Pair { first: &str, second: &str }
B. struct Pair<'a> { first: &'a str, second: &'a str }
C. struct Pair<'a, 'b> { first: &'a str, second: &'b str }
D. struct Pair<'a> { first: &'a str, second: &str }

Solution

  1. Step 1: Understand multiple lifetimes in structs

    When fields have different lifetimes, declare multiple lifetime parameters.
  2. Step 2: Match declaration to fields

    Each field uses its own lifetime parameter, so struct must declare both 'a and 'b.
  3. Final Answer:

    struct Pair<'a, 'b> { first: &'a str, second: &'b str } -> Option C
  4. Quick Check:

    Different lifetimes need separate parameters [OK]
Hint: Use separate lifetime parameters for different references [OK]
Common Mistakes:
  • Using one lifetime for different lifetime references
  • Omitting lifetime parameters entirely
  • Mixing owned and borrowed types without lifetimes
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard