We’re making a change to Kotlin that makes inline lambdas truly first-class language constructs, and makes them truly seamless to use. We do so by addressing a long-standing inconsistency when it comes to using break and continue inside lambdas.

In short: Kotlin becomes more consistent! And it does so by now experimentally supporting break and continue statements in a non-local manner, analog to nonlocal return expressions. This gets you more flexibility when you’re writing code where you have loops combined with inline functions that have lambda parameters – plus it finally makes inline lambdas real first-class language constructs.

This becomes super useful when you work with scope functions like let, apply, run, also, and with, when you work with mutexes or locks in Kotlin coroutines, or when you work with the Result type to do more functional error handling!