Why enums are used in Rust - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use enums in Rust?

Which of the following best explains why enums are used in Rust?

A Enums are used to create mutable variables that can change types at runtime.

B Enums automatically optimize memory usage by compressing all variants into a single byte.

C Enums replace structs and classes entirely in Rust for all data storage.

D Enums allow grouping related values under one type, making code safer and clearer.

💡 Hint

Think about how enums help organize different but related data options.

Enums let you define a type that can be one of several variants. This helps write safer code by handling all possible cases explicitly.

❓ Predict Output

intermediate

Output of enum match in Rust

What is the output of this Rust code?

Rust

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

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

A Going West

B Going North

C Going East

D Compilation error

💡 Hint

Look at the value assigned to dir and which match arm it triggers.

The variable dir is set to Direction::East, so the match prints "Going East".

❓ Predict Output

advanced

What error does this enum code raise?

What error will this Rust code produce?

Rust

enum Status {
    Ok(u32),
    Err(String),
}

fn main() {
    let s = Status::Ok(200);
    match s {
        Status::Ok(code) => println!("Code: {}", code),
        Status::Err(msg) => println!("Error occurred"),
    }
}

A Error: pattern `Status::Err` does not match enum variant with data

B No error, prints 'Code: 200'

C Error: missing semicolon after println!

D Error: cannot match on enum with data

💡 Hint

Check how the Status::Err variant is matched compared to its definition.

The Status::Err variant carries a String value, so the match arm must include a variable to capture it, e.g., Status::Err(msg).

🚀 Application

advanced

How many variants does this enum have?

Consider this Rust enum. How many distinct variants does it have?

Rust

enum Message {
    Quit,
    Move { x: i32, y: i32 },
    Write(String),
    ChangeColor(i32, i32, i32),
}

A 5

B 4

C 1

D 3

💡 Hint

Count each variant name listed inside the enum.

The enum has four variants: Quit, Move, Write, and ChangeColor.

🧠 Conceptual

expert

Why prefer enums over multiple structs?

Why might a Rust programmer prefer using an enum instead of multiple separate structs for related data?

A Enums allow grouping related data types under one type, enabling exhaustive checks and simpler code.

B Enums automatically generate getter and setter methods for all fields.

C Enums use less memory than any combination of structs regardless of data.

D Enums can be mutated to change their variant type at runtime.

💡 Hint

Think about how enums help the compiler check all possible cases.

Enums group related variants into one type, so the compiler can ensure all cases are handled, making code safer and easier to maintain.

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