> In C-like languages exiting from a deeply nested loop isn’t exactly trivial (without the use of goto, so don’t even go there). What's wrong with goto to do e

> In C-like languages exiting from a deeply nested loop isn’t exactly trivial (without the use of goto, so don’t even go there). What's wrong with goto to do exactly what it's supposed to do? You can of course wrap loop content into functions, and maybe the compiler will "out-optimize" that, but you will never get the performance of loops in a single function, nor you can conditionally jump from middle of one loop into another.