I think the 'debate' only makes sense in a sufficiently low-level language, at which point you're already taking safety into your own hands. In a higher-level

I think the 'debate' only makes sense in a sufficiently low-level language, at which point you're already taking safety into your own hands. In a higher-level language, it's as silly as asking if you should avoid explicit malloc/free when writing SQL. How would the Rust compiler deal with goto? You could dodge ownership and start operating on data before/after it's created/deleted. A try-with-resources/using in Java/C# would no longer offer its guarantees. How about async blocks in general? Do you just wander into another thread's code (but keep your own stack frame?) Lambdas? Closures? People probably > regurgitate the age old argument against the use of goto because there's no new arguments for it.