break and continue
About this video
The video shows how break and continue change a loop's normal control flow. break immediately terminates the loop, which is useful in a climate simulation that should stop and warn when temperature hits a limit; continue skips the rest of the current iteration, which helps an online store reject oversized orders without deep nesting. Both are usually combined with a conditional and shouldn't replace meaningful loop conditions.
You'll be able to
- describe what break and continue do to a loop's control flow.
- trace how many times parts of a loop body run when break or continue is inside a conditional.
- choose break or continue for a situation and explain why.
Key words
- break
- A statement that immediately terminates the loop, skipping any remaining lines in the body.
- continue
- A statement that skips the rest of the current iteration and jumps back to the top of the loop for the next one.
- control flow
- The order in which the computer executes the lines of a program.
- compound loop condition
- A loop condition that combines several checks, for example on both the year and the temperature.
- nesting
- Placing code blocks inside other blocks, like an if inside an else inside a while.
Transcript
- [Instructor] We may sometimes want to alter the normal control flow of our loops to either terminate early or skip an iteration. To do this, we can use the break and continue statements. A break statement tells the computer to immediately terminate the loop.
We write it with just the keyword, break. Normally, this loop repeats 100 times, but if I add a break statement here, it only repeats once, or really even 1/2 times. We execute this first print statement, then we hit the break, and that tells us to immediately exit the loop.
so we skip any remaining lines of code inside the loop body. Now this code isn't particularly useful. Why have a loop if I'm just gonna terminate it immediately? Instead, we typically combine a break statement with a conditional, So we only execute the break if a certain condition becomes true.
Now, the break statement only executes when I, the loop variable reaches 10. So the loop repeats a full 10 times before it hits this break statement and terminates. Better, but why have the loop repeat 100 times in the first place if it's always going to exit on the 11th iteration?
Let's take a look at a real example where a break statement might actually be useful. Here I have a very simple climate simulation that models global temperature change based on CO2 emissions. My team has determined that climate effects become critical when the global temperature reaches 15.8 degrees Celsius.
But if we do hit that limit, our simulation has already failed. We don't really care about measuring the temperature on subsequent years at that point. That means what we really want is to also terminate the loop. We don't want the computer to bother doing all this extra work on these calculations that we don't care about.
So maybe I think about writing a compound loop condition that checks both the year and the temperature. But if the loop terminates because of the temperature case, I still wanna print that warning. There are many different ways I can try and maneuver this code so both things happen where I terminate the loop if the temperature exceeds the limit and I print the warning.
However, the easiest way to accomplish both tasks is to use a break statement. Because I want something specific to happen under one of those termination conditions, it's better to use a conditional with a break statement instead of a compound loop condition. Then any code I wanna run before I terminate the loop in that case, I can just put inside the conditional.
The continue statement skips the rest of the current iteration of the loop. Execution immediately jumps back to the top of the loop, and then the computer continues with the next iteration as normal. Let's go back to our original example with a loop that repeats 100 times.
If I stick a continue statement in the middle, the computer skips the bottom half of the loop body on every iteration. It executes the first print statement and then it hits the continue. So it jumps back to the top of the loop to start the next iteration. That means we skip the rest of the current iteration so we don't execute this final print statement inside the loop body.
Again, not super useful. If we never execute this final print statement, why bother having it in the first place? Just like the break statement, we typically combine continue statements with a conditional. Now we only execute the continue statement when the loop variable i equals 10.
That means we're only skipping the bottom of the 11th iteration. Now let's take a look at a more realistic continue example. Here we have a loop to simulate an online store. We want to keep accepting orders for jars of jam until we run out of inventory, but we wanna add some input validation so we don't accidentally sell more jars than we have in case we end up in a situation where we only have a few jars left and a huge bulk order comes in.
So maybe we add a conditional here that checks that the order size is greater than the number of remaining jars, and we only process the order if the order size is okay. If an order comes in for 100 jars and we only have 10 left, we don't wanna shut down the store, we just wanna tell that specific user we can't fulfill their order right now, but continue to accept other orders to try and sell those last 10 jars.
All right, my loop works, but now I'm several layers of nesting deep. I have an if nested inside an else, nested inside a while, and with all this annotation going on, this code is kind of hard to read. This is where the continue statement comes to the rescue.
Instead of having this whole if else situation inside the loop body, I can just check the invalid condition and put a continue there. Then all this order processing code that I wanna run on a typical iteration doesn't have to be double nested. If the order size is too big, we'll hit the continuous statement and jump back to the top of the loop, which skips all the order processing code below it for that iteration.
Breaking continue statements are powerful tools for modifying the control flow of our loops. Break statements allow us to skip unnecessary work by terminating a loop early in an error case or in cases where we want to react to a specific termination condition.
Continue statements allow us to skip doing the work on iterations where we have invalid or non meaningful data, and they allow us to avoid deep nesting by checking for those invalid cases upfront. However, we should be careful about overly relying on break and continue.
They should never be substitutes for writing meaningful loop conditions in the first place.
Video © Khan Academy, used under CC BY-NC-SA. Watch on Khan Academy. Puzzicle is not affiliated with Khan Academy.