3 ms·
The article is hosted on some kind of shitty blog platform which doesn't let me copy quotes from it. Anyway, there was a point about how tedious it was to type,
by klodolph 5y ago
The article is hosted on some kind of shitty blog platform which doesn't let me copy quotes from it. Anyway, there was a point about how tedious it was to type,
return SomeStructName{}, err
This is what "goreturns" does.
Concise error handling would be "nice to have" but to be honest, I prefer Go's current error handling over exceptions, most of the time.
- kaba0 5y agoWhy do you prefer them over exceptions? What is the preferred way of handling errors deep in the stack in a unified place (eg. By displaying an error page)?