>> - Using a single goto and single label to exit several levels of scope.

> Better handled by putting the nested scope in a function and using `return`.

I dunno, that seems pretty silly to me. It's a perfectly valid use case of goto to jump out of deeply nested loops, and refactoring it to break out the inner loop in a function seems like pointless busy-work that ultimately makes the code harder to read, just so you can avoid a goto.