Creating struct instances in Rust - Performance & Efficiency

Time Complexity: Creating struct instances

O(n)

Understanding Time Complexity

When we create instances of a struct in Rust, we want to know how the time it takes changes as we create more instances.

We ask: How does the work grow when making many struct objects?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

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

fn create_points(n: usize) -> Vec {
    let mut points = Vec::new();
    for i in 0..n {
        points.push(Point { x: i as i32, y: i as i32 });
    }
    points
}
    

This code creates a list of n points, each with x and y set to the current index.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loop runs n times creating and adding a struct instance.
• How many times: Exactly once per point, so n times.

How Execution Grows With Input

Each new point takes about the same time to create and add, so total work grows evenly with n.

Input Size (n)	Approx. Operations
10	About 10 creations and insertions
100	About 100 creations and insertions
1000	About 1000 creations and insertions

Pattern observation: The work grows in a straight line as n grows.

Final Time Complexity

Time Complexity: O(n)

This means the time to create points grows directly with how many points you want.

Common Mistake

[X] Wrong: "Creating many struct instances is instant and does not depend on how many we make."

[OK] Correct: Each instance takes some time to build and store, so more instances mean more total time.

Interview Connect

Understanding how creating many objects affects time helps you reason about program speed and resource use in real projects.

Self-Check

"What if we added a nested loop inside the creation loop that does a fixed amount of work? How would the time complexity change?"

Practice

1. What is the correct way to create an instance of a struct Person with fields name and age in Rust?

easy

A. let p = new Person { name: "Alice", age: 30 };

B. let p = Person("Alice", 30);

C. let p = Person { name: String::from("Alice"), age: 30 };

D. let p = Person(name = "Alice", age: 30);

Solution

1. Step 1: Understand struct instance syntax

   In Rust, you create a struct instance by naming the struct and assigning values to each field inside curly braces.

2. Step 2: Match the correct syntax

   let p = Person { name: String::from("Alice"), age: 30 }; uses Person { name: String::from("Alice"), age: 30 }, which is the correct way. Other options use incorrect syntax like tuple style or assignment inside parentheses.

3. Final Answer:

   let p = Person { name: String::from("Alice"), age: 30 }; -> Option C

4. Quick Check:

   Struct instance = StructName { field: value } [OK]

Hint: Use StructName { field: value } to create instances [OK]

Common Mistakes:

• Using parentheses instead of curly braces
• Trying to assign fields with = inside parentheses
• Forgetting to convert string literals to String type

2. Which of the following is a syntax error when creating a struct instance Car with fields make and year?

easy

A. let c = Car { make: String::from("Toyota"), year: 2020 };

B. let c = Car { make: "Toyota", year: 2020 };

C. let c = Car { make: String::from("Toyota"), year: "2020" };

D. let c = Car { make: String::from("Toyota"), year: 2020 }

Solution

1. Step 1: Check for syntax errors

   let c = Car { make: String::from("Toyota"), year: 2020 } is missing the semicolon after the let statement, which causes a syntax error in Rust.

2. Step 2: Review other options

   Options A, B, and C have semicolons and valid struct syntax, though B and C may cause type errors if field types do not match.

3. Final Answer:

   let c = Car { make: String::from("Toyota"), year: 2020 } -> Option D

4. Quick Check:

   Semicolon required after let statements [OK]

Hint: Match field types exactly when creating struct instances [OK]

Common Mistakes:

• Assigning string literals where String is expected without conversion
• Using wrong data types for fields
• Omitting semicolons (sometimes allowed but risky)

3. Given the struct and instance creation below, what will be printed?

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

fn main() {
    let p = Point { x: 5, y: 10 };
    println!("({}, {})", p.x, p.y);
}

medium

A. (5, 10)

B. (10, 5)

C. (x, y)

D. Compilation error

Solution

1. Step 1: Understand struct fields and instance values

   The struct Point has fields x and y. The instance p assigns x = 5 and y = 10.

2. Step 2: Analyze the print statement

   The println! macro prints the values of p.x and p.y in order, so output is (5, 10).

3. Final Answer:

   (5, 10) -> Option A

4. Quick Check:

   Print fields in order = (5, 10) [OK]

Hint: Print fields in order they appear in code [OK]

Common Mistakes:

• Mixing up field order in print
• Expecting field names printed instead of values
• Assuming compilation error without reason

4. Identify the error in the following code that tries to create a struct instance:

struct Book {
    title: String,
    pages: u32,
}

fn main() {
    let b = Book { title: "Rust Book", pages: 300 };
}

medium

A. Missing semicolon after struct definition

B. String literal assigned directly to String field without conversion

C. Field name 'pages' is misspelled

D. Struct instance missing field values

Solution

1. Step 1: Check field types and assigned values

   The field title is of type String, but the code assigns a string literal "Rust Book" directly, which is a "str" type, causing a type mismatch.

2. Step 2: Confirm other parts are correct

   The field pages is correctly assigned an integer. The struct definition and instance have correct syntax otherwise.

3. Final Answer:

   String literal assigned directly to String field without conversion -> Option B

4. Quick Check:

   Convert "str" to String with String::from() [OK]

Hint: Convert string literals to String with String::from() [OK]

Common Mistakes:

• Assigning "str" directly to String fields
• Misspelling field names
• Omitting required fields in instance

5. You have a struct Employee with fields name: String, id: u32, and active: bool. How do you create a new instance with name as "John", id as 101, and active as true, using shorthand for the active field if you have a variable active set to true?

hard

A. let active = true;
let e = Employee { name: String::from("John"), id: 101, active };

B. let active = true;
let e = Employee { name: "John", id: 101, active: active };

C. let e = Employee { name: String::from("John"), id: 101, active: true };

D. let active = true;
let e = Employee { name: String::from("John"), id: 101, active = active };

Solution

1. Step 1: Understand field shorthand syntax

   If a variable name matches a struct field name, you can use shorthand by just writing the variable name without field: value.

2. Step 2: Identify correct usage

   let active = true; let e = Employee { name: String::from("John"), id: 101, active }; uses shorthand correctly: active variable is used directly as a field. let active = true; let e = Employee { name: "John", id: 101, active: active }; uses explicit active: active but has type mismatch on name. let e = Employee { name: String::from("John"), id: 101, active: true }; does not use the variable. let active = true; let e = Employee { name: String::from("John"), id: 101, active = active }; uses invalid syntax with = inside struct initialization.

3. Final Answer:

   let active = true; let e = Employee { name: String::from("John"), id: 101, active }; -> Option A

4. Quick Check:

   Use shorthand when variable name matches field name [OK]

Hint: Use field shorthand: just write variable name if it matches field [OK]

Common Mistakes:

• Using = instead of : in struct initialization
• Not converting string literals to String
• Not using shorthand when possible