[aflag]

I wasn't suggesting go changes. I was just replying to

> > every error must be handled explicitly, and every control flow path must be made obvious, no matter how much verbosity this creates.

> Is this, bad? It is just the recommended way. You are not required to implement your code in this way.

Pointing out that it is not the recommended way, it is really the only sane way to do it in go. And, in my opinion, that's bad design.

[tapirl]

Loop back: you can use the panic/recover way.

> ... that's bad design.

This is a subjective opinion. Many people don't think so.