Why enums are used in Rust - Performance Analysis

Time Complexity: Why enums are used

O(1)

Understanding Time Complexity

Enums let us group different kinds of values under one name. Understanding their time cost helps us see how fast programs run when using enums.

We ask: How does using enums affect the steps a program takes as data grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

enum Shape {
    Circle(f64),
    Rectangle(f64, f64),
    Square(f64),
}

fn area(shape: &Shape) -> f64 {
    match shape {
        Shape::Circle(radius) => 3.14 * radius * radius,
        Shape::Rectangle(width, height) => width * height,
        Shape::Square(side) => side * side,
    }
}
    

This code defines different shapes using an enum and calculates their area by checking the shape type.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The match statement checks the shape variant once per call.
• How many times: Exactly once for each area calculation; no loops or recursion here.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: Each shape requires one check, so operations grow directly with the number of shapes.

Final Time Complexity

Time Complexity: O(1)

This means the time to calculate the area of a single shape is constant, regardless of the shape type.

Common Mistake

[X] Wrong: "Enums slow down programs a lot because they check many types every time."

[OK] Correct: Each check happens only once per item, so the cost grows steadily, not wildly. Enums keep code clear without big slowdowns.

Interview Connect

Knowing how enums work and their time cost shows you understand safe and clear code design. This skill helps you explain your choices calmly and confidently.

Self-Check

"What if the area function used recursion to handle nested enums? How would the time complexity change?"

Practice

1. Why are enums used in Rust programming?

easy

A. To group related values under one type name

B. To perform mathematical calculations faster

C. To store large amounts of unrelated data

D. To replace all functions with a single keyword

Solution

1. Step 1: Understand the purpose of enums

   Enums allow grouping of related options or variants under one type name, making code organized.

2. Step 2: Compare other options

   Options A, B, and D do not describe the main use of enums. Enums are not for math speed, unrelated data storage, or replacing functions.

3. Final Answer:

   To group related values under one type name -> Option A

4. Quick Check:

   Enums group related options = C [OK]

Hint: Enums group related choices under one name [OK]

Common Mistakes:

• Thinking enums speed up math operations
• Confusing enums with arrays or structs
• Believing enums replace functions

2. Which of the following is the correct way to define an enum in Rust?

easy

A. enum Color { Red, Green, Blue }

B. enum Color = { Red, Green, Blue }

C. enum Color: Red, Green, Blue

D. enum Color -> { Red, Green, Blue }

Solution

1. Step 1: Recall Rust enum syntax

   Rust enums are defined using the keyword enum followed by the name and curly braces containing variants separated by commas.

2. Step 2: Check each option

   enum Color { Red, Green, Blue } matches correct syntax. Options A, B, and C use invalid symbols (=, :, ->) which are not part of enum syntax.

3. Final Answer:

   enum Color { Red, Green, Blue } -> Option A

4. Quick Check:

   Correct enum syntax uses braces and commas = D [OK]

Hint: Remember enum uses braces and commas, no equal sign [OK]

Common Mistakes:

• Using '=' instead of braces
• Using ':' or '->' after enum name
• Omitting commas between variants

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

enum Direction {
    North,
    East,
    South,
    West,
}

fn main() {
    let dir = Direction::East;
    match dir {
        Direction::North => println!("Going North"),
        Direction::East => println!("Going East"),
        Direction::South => println!("Going South"),
        Direction::West => println!("Going West"),
    }
}

medium

A. Going North

B. Going East

C. Going South

D. Going West

Solution

1. Step 1: Identify the enum variant assigned

   The variable dir is assigned Direction::East.

2. Step 2: Match statement output

   The match checks dir and prints the string for the matching variant. Since dir is East, it prints "Going East".

3. Final Answer:

   Going East -> Option B

4. Quick Check:

   Match prints variant name = A [OK]

Hint: Match prints message for assigned enum variant [OK]

Common Mistakes:

• Confusing variant names in match arms
• Assuming default output without match
• Ignoring enum variant assigned

4. Find the error in this Rust enum usage:

enum Status {
    Active,
    Inactive,
}

fn main() {
    let s = Status::active;
    match s {
        Status::Active => println!("Active"),
        Status::Inactive => println!("Inactive"),
    }
}

medium

A. Match arms should use lowercase variants

B. Missing semicolon after enum definition

C. Enum variants must be capitalized exactly

D. Enum cannot be used inside match statements

Solution

1. Step 1: Check enum variant usage

   Rust enum variants are case sensitive and usually start with uppercase letters. The code uses Status::active instead of Status::Active.

2. Step 2: Verify match arms and syntax

   Match arms use correct capitalization. No semicolon is needed after enum. Enums can be matched.

3. Final Answer:

   Enum variants must be capitalized exactly -> Option C

4. Quick Check:

   Enum variant names are case sensitive = A [OK]

Hint: Enum variants are case sensitive and capitalized [OK]

Common Mistakes:

• Using lowercase enum variants
• Adding unnecessary semicolons after enum
• Thinking enums can't be matched

5. You want to represent a shape that can be either a Circle with a radius or a Rectangle with width and height. Why is using an enum the best choice in Rust?

hard

A. Because enums automatically calculate area for shapes

B. Because enums are faster than structs for storing data

C. Because enums store all shapes as the same data type without variants

D. Because enums can hold different data types for each variant safely

Solution

1. Step 1: Understand enum variant data

   Rust enums can hold different data types for each variant, like a radius for Circle and width/height for Rectangle.

2. Step 2: Compare other options

   Enums do not automatically calculate area (A), nor store all shapes as same data without variants (C). Speed (D) is not the main reason.

3. Final Answer:

   Because enums can hold different data types for each variant safely -> Option D

4. Quick Check:

   Enums hold variant-specific data = B [OK]

Hint: Enums hold different data per variant safely [OK]

Common Mistakes:

• Thinking enums calculate values automatically
• Confusing enums with structs storing same data
• Assuming enums are always faster than structs