gotos

If you have goto, however, you don't need TCO, but then you're programming with gotos.

Anyways, exceptions are sort of gotos or at least they can behave that way.

And if you want a better performance, you can replace this switch with computed gotos (supported at least by gcc and clang).

Of course, then you're programming with gotos, which may not be awesome.

A bitecode interpreter is another place where it's nice to have gotos.

But sometimes speed matters, and good luck writing this without gotos.

State machines, for example, can make good use of gotos.

I don't follow you, what do computed gotos have to do with threaded code?

And it's true, as @pflanze's comment correctly points out and I think you're getting at, that loops aren't sufficient – but gotos are.

It's unrelated to gotos in a state machine.

Start with libncurses: I promise there's a few gotos where needed.

It's basically just arithmetic, comparisons, i/o, and gotos, right?

Also if I understood you correctly what you're proposing doesn't have much to do with the "computed gotos" extension.

As soon as I say, "I wish I had X-language had gotos", I see jaws drop.

But my gotos always go "down" the source code, never "up.

> doesn't have much to do with the "computed gotos" extension You cannot implement indirect threaded code without a computed goto.