Why Match guards in Rust? - Purpose & Use Cases

The Big Idea

Discover how a simple extra check in patterns can save you from messy, buggy code!

The Scenario

Imagine you have a list of numbers and you want to do different things depending on their value, but only if they meet extra conditions, like being even or greater than 10.

Without match guards, you have to write many nested if-else checks inside each match arm, making your code long and confusing.

The Problem

Manually checking conditions inside each match arm leads to repeated code and mistakes.

It's easy to forget a condition or mix them up, causing bugs.

Also, the code becomes hard to read and maintain.

The Solution

Match guards let you add extra conditions directly to each match arm.

This keeps your code clean, readable, and easy to follow.

You write the condition once, right next to the pattern it applies to.

Before vs After

✗ Before

match num {
    _ => {
        if num % 2 == 0 {
            println!("Even number");
        } else if num > 10 {
            println!("Greater than 10");
        } else {
            println!("Other");
        }
    }
}

✓ After

match num {
    x if x % 2 == 0 => println!("Even number"),
    x if x > 10 => println!("Greater than 10"),
    _ => println!("Other")
}

What It Enables

You can write clear, concise code that handles complex conditions directly in pattern matching.

Real Life Example

When processing user input commands, you can match the command type and add guards to check if the user has the right permissions before running the command.

Key Takeaways

Match guards add extra conditions to match arms.

They make code easier to read and less error-prone.

They help handle complex logic cleanly in pattern matching.

Practice

1.

What is the purpose of a match guard in Rust?

easy

A. To add an extra condition to a pattern in a match statement

B. To replace the entire match statement with an if statement

C. To declare a new variable inside a match arm

D. To loop over all patterns automatically

Solution

1. Step 1: Understand match guards

   Match guards add extra conditions to patterns in a match, allowing more precise checks.

2. Step 2: Compare options

   Only To add an extra condition to a pattern in a match statement correctly describes adding extra conditions to patterns.

3. Final Answer:

   To add an extra condition to a pattern in a match statement -> Option A

4. Quick Check:

   Match guard = extra condition [OK]

Hint: Match guards add conditions after patterns using if [OK]

Common Mistakes:

• Thinking match guards replace match statements
• Confusing match guards with variable declarations
• Assuming match guards loop over patterns

2.

Which of the following is the correct syntax for a match guard in Rust?

match x {
    5 if x > 3 => println!("Greater than 3"),
    _ => println!("Other")
}

easy

A. match x { if 5 > 3 => println!("Greater than 3"), _ => println!("Other") }

B. match x { 5 => if x > 3 { println!("Greater than 3") }, _ => println!("Other") }

C. match x { 5 if x > 3 => println!("Greater than 3"), _ => println!("Other") }

D. match x { 5 => println!("Greater than 3") if x > 3, _ => println!("Other") }

Solution

1. Step 1: Identify correct match guard syntax

   Match guards use pattern if condition => expression syntax.

2. Step 2: Check options

   match x { 5 if x > 3 => println!("Greater than 3"), _ => println!("Other") } correctly places if x > 3 after the pattern 5.

3. Final Answer:

   match x { 5 if x > 3 => println!("Greater than 3"), _ => println!("Other") } -> Option C

4. Quick Check:

   Pattern if condition => action [OK]

Hint: Use 'pattern if condition => action' for match guards [OK]

Common Mistakes:

• Placing if before the pattern
• Using if inside the match arm block
• Putting if after the expression

3.

What will be the output of the following Rust code?

let num = 7;
match num {
    n if n < 5 => println!("Less than 5"),
    n if n <= 10 => println!("Between 5 and 10"),
    _ => println!("Greater than 10"),
}

medium

A. Between 5 and 10

B. No output (compile error)

C. Greater than 10

D. Less than 5

Solution

1. Step 1: Evaluate match arms in order

   num is 7, first guard checks if 7 < 5 (false), so skip.

2. Step 2: Check second guard

   7 <= 10 is true, so this arm runs and prints "Between 5 and 10".

3. Final Answer:

   Between 5 and 10 -> Option A

4. Quick Check:

   7 ≤ 10 matches second guard [OK]

Hint: Match arms checked top to bottom; first true guard runs [OK]

Common Mistakes:

• Assuming first guard matches 7
• Thinking all guards run
• Confusing output with compile error

4.

Identify the error in this Rust code using match guards:

let x = 10;
match x {
    n if n > 5 => println!("Greater than 5"),
    n if n > 8 => println!("Greater than 8"),
    _ => println!("Other"),
}

medium

A. Syntax error: match guards cannot use variables

B. The wildcard pattern must come before guarded patterns

C. Missing semicolon after println! macros

D. The second guard is unreachable because the first guard covers all cases greater than 5

Solution

1. Step 1: Analyze guard order and coverage

   The first guard matches all n > 5, so it includes all n > 8 as well.

2. Step 2: Identify unreachable code

   The second guard is never reached because the first guard catches those values first.

3. Final Answer:

   The second guard is unreachable because the first guard covers all cases greater than 5 -> Option D

4. Quick Check:

   First guard shadows second guard [OK]

Hint: Order guards from most specific to least specific [OK]

Common Mistakes:

• Ignoring unreachable code warnings
• Thinking guards can overlap safely
• Misunderstanding guard evaluation order

5.

Given a list of integers, write a Rust match expression with match guards to print:

• "Small" if the number is less than 10
• "Medium" if the number is between 10 and 20 (inclusive)
• "Large" if the number is greater than 20

Which of the following match arms correctly implements this logic for a variable n?

hard

A. match n {
x if x <= 10 => println!("Small"),
x if x > 10 && x < 20 => println!("Medium"),
_ => println!("Large"),
}

B. match n {
x if x < 10 => println!("Small"),
x if x >= 10 && x <= 20 => println!("Medium"),
_ => println!("Large"),
}

C. match n {
x if x < 10 => println!("Small"),
x if x > 20 => println!("Medium"),
_ => println!("Large"),
}

D. match n {
x if x < 10 => println!("Small"),
x if x > 10 && x < 20 => println!("Medium"),
_ => println!("Large"),
}

Solution

1. Step 1: Check conditions for each size category

   "Small" is for n < 10, "Medium" for 10 ≤ n ≤ 20, "Large" for n > 20.

2. Step 2: Verify each match arm

   match n { x if x < 10 => println!("Small"), x if x >= 10 && x <= 20 => println!("Medium"), _ => println!("Large"), } correctly uses x < 10, x >= 10 && x <= 20, and wildcard for others.

3. Final Answer:

   match n { x if x < 10 => println!("Small"), x if x >= 10 && x <= 20 => println!("Medium"), _ => println!("Large"), } -> Option B

4. Quick Check:

   Guards match exact ranges [OK]

Hint: Use inclusive ranges with && for medium category [OK]

Common Mistakes:

• Using wrong comparison operators
• Overlapping ranges causing unreachable arms
• Missing inclusive bounds for medium range