Struct update syntax in Rust - Step-by-Step Execution

Concept Flow - Struct update syntax

Create new struct instance

↓

Specify fields to update

↓

Use .. to copy remaining fields

↓

New struct with updated and copied fields

This flow shows how to create a new struct instance by updating some fields and copying the rest from another instance using .. syntax.

Execution Sample

Rust

struct Point {
    x: i32,
    y: i32,
}

fn main() {
    let p1 = Point { x: 5, y: 10 };
    let p2 = Point { x: 15, ..p1 };
}

Creates a new Point p2 with x updated to 15 and y copied from p1.

Execution Table

Step	Action	Field x	Field y	Resulting struct
1	Create p1	5	10	Point { x: 5, y: 10 }
2	Create p2 with x=15, copy y from p1	15	10	Point { x: 15, y: 10 }
3	End	-	-	p2 is Point { x: 15, y: 10 }

💡 Struct p2 created with updated x and copied y from p1.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
p1.x	-	5	5	5
p1.y	-	10	10	10
p2.x	-	-	15	15
p2.y	-	-	10	10

Key Moments - 2 Insights

Why does p2.y have the same value as p1.y even though we didn't specify it?

Because of the ..p1 syntax in step 2, which copies all fields from p1 that are not explicitly set in p2, as shown in the execution_table row 2.

What happens if we omit the ..p1 part when creating p2?

Then p2 must specify all fields explicitly. Otherwise, the code will not compile because Rust requires all fields to be initialized.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of p2.y after step 2?

A 10

B 15

C 0

D Undefined

💡 Hint

Check the 'Field y' column in row 2 of the execution_table.

At which step is the struct p1 created?

A Step 2

B Step 3

C Step 1

D Before Step 1

💡 Hint

Look at the 'Action' column in the execution_table for when p1 is created.

If we change p2's x to 20 in step 2, what will be p2.x and p2.y values?

A p2.x = 15, p2.y = 10

B p2.x = 20, p2.y = 10

C p2.x = 20, p2.y = 0

D p2.x = 5, p2.y = 10

💡 Hint

Refer to how the update syntax changes only specified fields, copying others from p1.

Concept Snapshot

Struct update syntax in Rust:
- Use .. to copy remaining fields from another instance.
- Syntax: let new = Struct { field1: val, ..old };
- Only specify fields you want to change.
- Other fields are copied from old instance.
- Helps avoid repetition when creating similar structs.

Full Transcript

This example shows how to create a new struct instance by updating some fields and copying the rest from an existing instance using Rust's struct update syntax. First, p1 is created with x=5 and y=10. Then p2 is created with x=15 and y copied from p1 using ..p1. The execution table traces these steps and shows the values of fields after each step. The variable tracker shows how each field changes or stays the same. Key moments clarify why fields are copied and what happens if ..p1 is omitted. The quiz tests understanding of field values and struct creation steps. The snapshot summarizes the syntax and usage of struct update syntax in Rust.

Practice

1. What does the Rust struct update syntax ..old_struct do when creating a new struct?

easy

A. Copies all remaining fields from old_struct to the new struct

B. Deletes the old_struct after creating the new struct

C. Moves all fields from old_struct without copying

D. Creates a reference to old_struct instead of a new struct

Solution

1. Step 1: Understand struct update syntax

   The syntax ..old_struct copies all fields from old_struct that are not explicitly set in the new struct.

2. Step 2: Effect on new struct creation

   This lets you create a new struct with some fields changed, while reusing the rest from old_struct.

3. Final Answer:

   Copies all remaining fields from old_struct to the new struct -> Option A

4. Quick Check:

   Struct update syntax copies fields [OK]

Hint: Remember: ..old_struct copies leftover fields [OK]

Common Mistakes:

• Thinking it moves fields instead of copying
• Assuming it deletes the old struct
• Confusing it with references

2. Which of the following is the correct way to use struct update syntax in Rust?

easy

A. let new_user = User { name: "Alice"; ..old_user };

B. let new_user = User { name: "Alice", ..old_user };

C. let new_user = User { name: "Alice" ..old_user };

D. let new_user = User { ..old_user, name: "Alice" };

Solution

1. Step 1: Check correct syntax order

   In Rust, fields you want to change come first, then ..old_struct copies the rest.

2. Step 2: Identify correct punctuation and placement

   let new_user = User { name: "Alice", ..old_user }; correctly places ..old_user after the changed field with commas separating fields.

3. Final Answer:

   let new_user = User { name: "Alice", ..old_user }; -> Option B

4. Quick Check:

   Changed fields first, then ..old_struct [OK]

Hint: Put changed fields before ..old_struct [OK]

Common Mistakes:

• Placing ..old_struct before changed fields
• Missing commas between fields
• Using semicolons inside struct initialization

3. Given the code:

struct Point { x: i32, y: i32 }

let p1 = Point { x: 5, y: 10 };
let p2 = Point { x: 8, ..p1 };
println!("({}, {})", p2.x, p2.y);

What is the output?

medium

A. (8, 0)

B. (5, 10)

C. Compilation error

D. (8, 10)

Solution

1. Step 1: Analyze struct initialization for p2

   p2 sets x to 8 explicitly, and copies y from p1 (which is 10) using struct update syntax.

2. Step 2: Determine printed values

   Printing p2.x and p2.y outputs (8, 10).

3. Final Answer:

   (8, 10) -> Option D

4. Quick Check:

   Changed x=8, copied y=10 [OK]

Hint: Changed fields override, others copy from old struct [OK]

Common Mistakes:

• Assuming y resets to 0
• Thinking x stays 5
• Expecting a compile error

4. What is wrong with this Rust code?

struct User { name: String, age: u32 }

let old_user = User { name: String::from("Bob"), age: 30 };
let new_user = User { age: 25, ..old_user };
println!("{} is {} years old", new_user.name, new_user.age);

medium

A. It causes a syntax error due to missing commas

B. It causes a move error because old_user is partially moved

C. It compiles and runs without errors

D. It prints wrong age value

Solution

1. Step 1: Understand ownership with struct update

   Using ..old_user moves non-Copy fields like name (String) that are not explicitly overridden, while age is overridden with a new value.

2. Step 2: Check usage of old_user

   old_user is not used after the update, so no ownership error occurs. The code compiles and runs, printing "Bob is 25 years old".

3. Final Answer:

   It compiles and runs without errors -> Option C

4. Quick Check:

   Non-Copy fields moved, but old_user not reused [OK]

Hint: Non-Copy fields move with ..old_struct, but OK if old not reused [OK]

Common Mistakes:

• Thinking it causes a partial move error
• Expecting automatic cloning of String
• Assuming syntax error instead of checking ownership

5. You have a struct:

struct Config { debug: bool, version: u32, name: String }

You want to create a new Config with debug set to true, keep version the same, and change name to "NewApp". Which code correctly uses struct update syntax and avoids ownership errors?

hard

A. let new_config = Config { debug: true, name: String::from("NewApp"), ..old_config };

B. let new_config = Config { debug: true, ..old_config, name: String::from("NewApp") };

C. let new_config = Config { debug: true, name: "NewApp", ..old_config };

D. let new_config = Config { debug: true, name: old_config.name, ..old_config };

Solution

1. Step 1: Place changed fields before struct update

   Changed fields debug and name must come before ..old_config.

2. Step 2: Avoid ownership errors by creating new String

   Since name is a String, assign a new String with String::from("NewApp") to avoid moving old_config.name.

3. Final Answer:

   let new_config = Config { debug: true, name: String::from("NewApp"), ..old_config }; -> Option A

4. Quick Check:

   Changed fields first, clone String to avoid move [OK]

Hint: Clone or create new String before ..old_struct [OK]

Common Mistakes:

• Placing ..old_config before changed fields
• Using string literal instead of String::from
• Moving old_config.name causing ownership error