Yeah, that's handy, but goto is strictly more powerful than is needed for that. Languages with a loop-specific break (e.g. Java) can do that. You can kind of hack it to jump to the end by labeling and using do...while (false).

Scala does one better and simply defines a construct that allows you to exit early (boundary, which defines a code block that you can break out of).

Both of these are strictly better than goto because you can't just go any random place, and in particular you can't jump into context that isn't there, you can only escape out to a broader context. And the Scala one is particularly nice because unlike loops which might be there to loop, not to manage control flow, the only purpose of boundary is to manage control flow, so when you see it you know what to expect.

(Scala being Scala, it also abstracts the idea of jumping to a boundary, and when you can both create and enact jumps in an abstracted way, then that there is a jump isn't necessarily clear any more. But the basic feature has enhanced clarity, and the non-basic feature, despite having the potential for losing clarity, is very, very effective at making code that does what you need even if "what you need" involves some control flow.)

With things like that, the only time I occasionally miss goto is if writing some weird finite state machine where my state is on the stack.