3 ms·
It does apply though. If you think error handling in Go is too verbose or boring, you're not solving a real problem. If you're trying to come up with design pat
by Cthulhu_ 5y ago
It does apply though. If you think error handling in Go is too verbose or boring, you're not solving a real problem. If you're trying to come up with design patterns and strategies - as described in the article - to see if you can shave off some code (at the cost of complexity and non-idiomatic code), you're not solving a real problem.
Software is never about the low level nitty gritty, and in these cases it's better to stick with what people expect to see / read. Don't make people think. I'm not smart enough to read your interesting error checking.