Dijkstra was arguing in favor of structured programming languages powerful enough that you didn't need GOTO. For example you mostly see GOTO for error handling

Dijkstra was arguing in favor of structured programming languages powerful enough that you didn't need GOTO. For example you mostly see GOTO for error handling in C, because C lacks a structured way for resource cleanup. Dijkstra certainly wasn't arguing you should use trick like do{...}while(false) to avoid using the GOTO keyword.