I'm more than happy with renaming the problem to "goto creates spurious scopes".
goto doesn't create any scopes. As I've already stated, the memory is being used when my is executed since that causes it push an instruction on the stack.
Ok, but again we could argue over the definition of the word "needed". "Needed" by the program writer or "needed" by an implementation that keeps scopes around that are not accessible to the program writer anymore?
The instruction is needed because it's virtually impossible to tell that the scope will never exit.
- A lot of things can throw exceptions.
- Including signal handlers.
- The program can change while it's running.
Even in the simplest cases, it would be extremely expensive to check, especially since this check would have to be performed at run-time.