yego.me
💡 Stop wasting time. Read Youtube instead of watch. Download Chrome Extension

break and continue | Intro to CS - Python | Khan Academy


4m read
·Nov 10, 2024

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 a hundred times, but if I add a break statement here, it only repeats once, or really even one half 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 going to 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 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 a hundred 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 want to 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 a limit and 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 want to 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 a hundred 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 want to 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 a hundred jars and we only have ten left, we don't want to shut down the store; we just want to tell that specific user we can't fulfill their order right now, but continue to accept other orders to try and sell those last ten jars.

Alright, 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 indentation 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 want to run on a typical iteration doesn’t have to be double nested. If the order size is too big, we'll hit the continue statement and jump back to the top of the loop, which skips all the order processing code below it for that iteration.

Break and 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 up front.

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.

More Articles

View All
15 Ways Technology Is Going to Disrupt the Financial Industry
Disruption is great. The drastic changes are scary, sure. But when you’re prepared for them, then you can ride that wave all the way to the top. The world of banking and finance is shifting into a totally new dimension, and knowledge gets you ahead of eve…
Negative frequency
I want to talk a little bit about one of the quirkier ideas in signal processing, and that’s the idea of negative frequency. This is a phrase that may not initially make any sense at all. What does it mean to be a negative frequency? Could there be a sine…
Long run supply when industry costs are increasing or decreasing | Microeconomics | Khan Academy
What we have here we can view as the long run equilibrium or long run steady state for a perfectly competitive market. Let’s say this is the market for apples and it was this idealized perfectly competitive situation where we have many firms producing. Th…
History of Fentanyl in America | Trafficked with Mariana van Zeller
I’m going deep inside the fentanyl pipeline to see exactly how it’s fueling the most devastating drug epidemic in U.S. history. Yeah, fentanyl is a synthetic opioid 50 to 100 times stronger than morphine, making it the most potent narcotic in clinical use…
Things You Don't Need To Be Successful
All right. So a lot of people aren’t going to agree with this list because honestly, they’re looking for excuses. But reality is, there are things you don’t really need in order to be successful. Even though it might seem that way. We know this from perso…
Michael Burry's BIG Bet On Inflation (The Big Short 2.0?)
Well, earlier in the week, we did a deep dive into Michael Burry’s put option position against Tesla. But that wasn’t even the biggest takeaway from Cyan Asset Management’s 13F filing this quarter. The most alarming thing you find when you read between th…