Continue, break, loop, return.

Understanding control flow in Rust

This is an easy Rust question that tests your grasp of fundamental control-flow statements: loop, continue, break, and return. It's the kind of language-mechanics check that interviewers use early in a Rust round to confirm you can read and predict code behaviour without ambiguity.

To solve problems like this, you need to trace execution step by step, paying close attention to how each statement changes program flow. The question rewards precision: a single misread of when a loop exits or when a value is returned will lead to the wrong answer. This is especially important in Rust, where ownership and control flow interact in subtle ways.

• Loop termination and early exit patterns
• Return values from loops and functions
• Shadowing and mutable state within loops