Why structs are used in Rust - Performance Analysis

Time Complexity: Why structs are used

O(1)

Understanding Time Complexity

We want to understand how using structs affects the time it takes for a program to run.

Specifically, we ask: How does organizing data with structs change the work done by the program?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

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

fn distance(p1: &Point, p2: &Point) -> f64 {
    let dx = (p2.x - p1.x) as f64;
    let dy = (p2.y - p1.y) as f64;
    (dx * dx + dy * dy).sqrt()
}
    

This code defines a struct to hold two numbers and a function to calculate distance between two points.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Simple arithmetic calculations on struct fields.
• How many times: Each calculation happens once per function call.

How Execution Grows With Input

Since the function works on fixed fields inside structs, the work stays the same no matter how many points exist elsewhere.

Input Size (n)	Approx. Operations
10	Same small number of calculations
100	Same small number of calculations
1000	Same small number of calculations

Pattern observation: The time does not grow with input size because the function only looks at two points.

Final Time Complexity

Time Complexity: O(1)

This means the time to run the function stays the same no matter how many points exist.

Common Mistake

[X] Wrong: "Using structs makes the program slower because it adds extra steps."

[OK] Correct: Structs just group data together; accessing their fields is simple and fast, so they don't slow down the program by themselves.

Interview Connect

Understanding how structs organize data without adding extra time helps you explain clear and efficient code design in interviews.

Self-Check

"What if the distance function had to calculate distances for a list of points instead of just two? How would the time complexity change?"

Practice

1. Why do Rust programmers use structs in their code?

easy

A. To group related data together under one name

B. To write faster loops

C. To create functions

D. To handle errors automatically

Solution

1. Step 1: Understand the purpose of structs

   Structs are used to combine multiple pieces of related data into one named unit.

2. Step 2: Compare with other options

   Loops, functions, and error handling are different concepts and not the main reason for structs.

3. Final Answer:

   To group related data together under one name -> Option A

4. Quick Check:

   Structs = Group related data [OK]

Hint: Structs bundle related info like a real-world object [OK]

Common Mistakes:

• Thinking structs are for loops or functions
• Confusing structs with error handling
• Believing structs speed up code automatically

2. Which of the following is the correct way to define a simple struct in Rust?

easy

A. struct Person: { name String, age u32 }

B. struct Person = (name: String, age: u32);

C. struct Person { name: String, age: u32 }

D. struct Person { name; String, age; u32 }

Solution

1. Step 1: Recall Rust struct syntax

   Rust structs use the format: struct Name { field1: Type1, field2: Type2 }.

2. Step 2: Check each option

   struct Person { name: String, age: u32 } matches the correct syntax. Options B, C, and D have syntax errors like wrong punctuation or missing colons.

3. Final Answer:

   struct Person { name: String, age: u32 } -> Option C

4. Quick Check:

   Correct struct syntax = struct Person { name: String, age: u32 } [OK]

Hint: Remember: fields use colon and commas inside braces [OK]

Common Mistakes:

• Using '=' instead of braces
• Missing colons between field names and types
• Using semicolons instead of commas

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

struct Point { x: i32, y: i32 }

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

medium

A. Compilation error

B. (5, 10)

C. Point { x: 5, y: 10 }

D. (10, 5)

Solution

1. Step 1: Understand struct field access

   The struct Point has fields x and y. The code creates p with x=5 and y=10.

2. Step 2: Analyze the print statement

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

3. Final Answer:

   (5, 10) -> Option B

4. Quick Check:

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

Hint: Print fields in order: x then y [OK]

Common Mistakes:

• Swapping x and y values
• Expecting debug print of whole struct
• Thinking code won't compile

4. Identify the error in this Rust struct usage:

struct Car {
    model: String,
    year: u32
}

fn main() {
    let my_car = Car { model: "Tesla", year: "2020" };
}

medium

A. Struct fields must be mutable

B. Missing semicolon after struct definition

C. Model field should be an integer

D. Year field has wrong type: string instead of u32

Solution

1. Step 1: Check struct field types

   The Car struct defines year as u32 (a number).

2. Step 2: Check struct initialization

   The code assigns year: "2020", which is a string, not a number. This causes a type mismatch error.

3. Final Answer:

   Year field has wrong type: string instead of u32 -> Option D

4. Quick Check:

   Field types must match exactly [OK]

Hint: Match field types exactly when creating structs [OK]

Common Mistakes:

• Using quotes around numbers
• Thinking fields must be mutable
• Missing semicolon is not the main error here

5. You want to model a Book with title, author, and number of pages using a Rust struct. Which approach best uses structs to organize this data?

hard

A. Use a struct with fields: title (String), author (String), pages (u32)

B. Use separate variables for title, author, and pages without a struct

C. Use a tuple with (String, String, u32) without naming fields

D. Use a struct with only one field holding all data as a single string

Solution

1. Step 1: Understand the goal of modeling data

   We want to group related properties of a book clearly and access them by name.

2. Step 2: Evaluate options for clarity and organization

   Use a struct with fields: title (String), author (String), pages (u32) uses a struct with named fields for each property, making code clear and organized. Use separate variables for title, author, and pages without a struct scatters data, Use a tuple with (String, String, u32) without naming fields uses unnamed tuple fields, and Use a struct with only one field holding all data as a single string mixes all data into one string, losing structure.

3. Final Answer:

   Use a struct with fields: title (String), author (String), pages (u32) -> Option A

4. Quick Check:

   Structs model real-world things with named properties [OK]

Hint: Use structs to name and group related data clearly [OK]

Common Mistakes:

• Using tuples without field names
• Storing all data in one string
• Avoiding structs and using separate variables