Loop labels in Rust - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to label the outer loop correctly.

Rust

fn main() {
    'outer: for i in 1..=3 {
        for j in 1..=3 {
            if i == 2 && j == 2 {
                break [1];
            }
            println!("i = {}, j = {}", i, j);
        }
    }
}

Drag options to blanks, or click blank then click option'

A'label

B'inner

C'loop

D'outer

Attempts:

3 left

💡 Hint

Common Mistakes

Using a label that is not defined.

Omitting the apostrophe in the label name.

The label 'outer is used to break out of the outer loop from inside the inner loop.

2fill in blank

medium

Complete the code to continue the outer loop when a condition is met.

Rust

fn main() {
    'outer: for i in 1..=3 {
        for j in 1..=3 {
            if j == 2 {
                continue [1];
            }
            println!("i = {}, j = {}", i, j);
        }
    }
}

Drag options to blanks, or click blank then click option'

A'inner

B'loop

C'outer

D'label

Attempts:

3 left

💡 Hint

Common Mistakes

Using continue without a label inside nested loops.

Using a label that does not exist.

Using continue with the 'outer label skips to the next iteration of the outer loop.

3fill in blank

hard

Fix the error in the code by choosing the correct label to break the outer loop.

Rust

fn main() {
    'start: for x in 1..=5 {
        for y in 1..=5 {
            if x * y > 6 {
                break [1];
            }
            println!("x = {}, y = {}", x, y);
        }
    }
}

Drag options to blanks, or click blank then click option'

A'start

B'outer

C'inner

D'loop

Attempts:

3 left

💡 Hint

Common Mistakes

Using a label that is not defined.

Using break without a label inside nested loops.

The label 'start is defined on the outer loop and must be used to break it.

4fill in blank

hard

Fill both blanks to correctly label and break the outer loop.

Rust

fn main() {
    [1] for num in 1..=4 {
        for letter in ['a', 'b', 'c'].iter() {
            if num == 3 {
                break [2];
            }
            println!("{} - {}", num, letter);
        }
    }
}

Drag options to blanks, or click blank then click option'

A'outer:

B'inner:

C'outer

D'inner

Attempts:

3 left

💡 Hint

Common Mistakes

Using the label with colon in the break statement.

Mismatching label names between loop and break.

The outer loop is labeled 'outer: and the break uses 'outer to exit it.

5fill in blank

hard

Fill all three blanks to label the loops and continue the outer loop correctly.

Rust

fn main() {
    [1] for i in 1..=3 {
        [2] for j in 1..=3 {
            if i == 2 && j == 1 {
                continue [3];
            }
            println!("i = {}, j = {}", i, j);
        }
    }
}

Drag options to blanks, or click blank then click option'

A'outer:

B'inner:

C'outer

D'inner

Attempts:

3 left

💡 Hint

Common Mistakes

Using the inner loop label in continue instead of the outer.

Including colon in the continue statement.

The outer loop is labeled 'outer:, inner loop 'inner:, and continue uses 'outer to skip to next outer iteration.

Practice

1. What is the main purpose of using loop labels in Rust?

easy

A. To create infinite loops without conditions.

B. To declare variables inside loops.

C. To name loops so you can break or continue specific loops inside nested loops.

D. To automatically parallelize loops for performance.

Solution

1. Step 1: Understand loop labels concept

   Loop labels let you assign a name to a loop, especially useful when loops are nested.

2. Step 2: Identify the use of labels

   Labels allow you to break or continue a specific loop by referring to its name, avoiding ambiguity.

3. Final Answer:

   To name loops so you can break or continue specific loops inside nested loops. -> Option C

4. Quick Check:

   Loop labels = control nested loops [OK]

Hint: Labels name loops for clear break/continue control [OK]

Common Mistakes:

• Thinking labels create infinite loops
• Confusing labels with variable declarations
• Assuming labels optimize performance automatically

2. Which of the following is the correct syntax to label a loop in Rust?

easy

A. label: loop { /* code */ }

B. loop label { /* code */ }

C. loop: label { /* code */ }

D. loop { label: /* code */ }

Solution

1. Step 1: Recall Rust loop label syntax

   In Rust, a loop label is written as 'label: before the loop keyword.

2. Step 2: Match syntax options

   label: loop { /* code */ } correctly places the label before the loop with a colon, e.g., 'label: loop {}.

3. Final Answer:

   label: loop { /* code */ } -> Option A

4. Quick Check:

   Label syntax = 'label: loop' [OK]

Hint: Labels come before loop with a colon [OK]

Common Mistakes:

• Placing label after loop keyword
• Using colon after loop instead of label
• Putting label inside loop body

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

fn main() {
    let mut count = 0;
    'outer: loop {
        println!("Outer loop: {}", count);
        let mut inner_count = 10;
        loop {
            println!("  Inner loop: {}", inner_count);
            if inner_count == 9 {
                break 'outer;
            }
            inner_count -= 1;
        }
        count += 1;
    }
    println!("Done");
}

medium

A. Outer loop: 0
Inner loop: 10
Inner loop: 9
Inner loop: 8
Done

B. Outer loop: 0
Inner loop: 10
Done

C. Infinite loop with no output

D. Outer loop: 0
Inner loop: 10
Inner loop: 9
Done

Solution

1. Step 1: Trace outer loop first iteration

   count starts at 0, prints "Outer loop: 0". Then inner loop starts with inner_count = 10.

2. Step 2: Trace inner loop and break condition

   Inner loop prints 10, then 9. When inner_count == 9, it breaks the 'outer loop, exiting both loops.

3. Final Answer:

   Outer loop: 0 Inner loop: 10 Inner loop: 9 Done -> Option D

4. Quick Check:

   Break 'outer stops both loops at inner_count 9 [OK]

Hint: Break 'label exits named loop immediately [OK]

Common Mistakes:

• Thinking break only exits inner loop
• Missing that break 'outer exits both loops
• Assuming loops continue infinitely

4. Identify the error in this Rust code using loop labels:

fn main() {
    'start: loop {
        loop {
            break start;
        }
    }
}

medium

A. Missing apostrophe before label name in break statement.

B. Label 'start' is not defined before use.

C. Cannot break a labeled loop from an inner loop.

D. Syntax error: break statements cannot have labels.

Solution

1. Step 1: Check break statement syntax

   In Rust, breaking a labeled loop requires the label with an apostrophe, e.g., break 'start;.

2. Step 2: Identify the missing apostrophe

   The code uses break start; missing the apostrophe before the label name, causing a syntax error.

3. Final Answer:

   Missing apostrophe before label name in break statement. -> Option A

4. Quick Check:

   Label break syntax = break 'label [OK]

Hint: Always prefix label with apostrophe in break/continue [OK]

Common Mistakes:

• Omitting apostrophe in break label
• Assuming labels are variables
• Thinking break can't target outer loops

5. Given nested loops labeled 'outer and 'inner, how can you skip the current iteration of the outer loop from inside the inner loop?

hard

A. Use break 'inner; inside the inner loop.

B. Use continue 'outer; inside the inner loop.

C. Use continue; without label inside the inner loop.

D. Use break 'outer; inside the inner loop.

Solution

1. Step 1: Understand continue with labels

   Using continue 'outer; skips the current iteration of the loop labeled 'outer, jumping to its next iteration.

2. Step 2: Differentiate break and continue

   break exits the loop, while continue skips to the next iteration. To skip outer loop iteration from inner loop, use continue 'outer;.

3. Final Answer:

   Use continue 'outer; inside the inner loop. -> Option B

4. Quick Check:

   continue 'label skips that loop iteration [OK]

Hint: Use continue 'label to skip outer loop iteration [OK]

Common Mistakes:

• Using break instead of continue to skip iteration
• Omitting label in continue statement
• Confusing break and continue effects