Dnia 2021-02-13, o godz. 17:44:47 Michael MacInnis <michael.p.macin...@gmail.com> napisał(a):
> I've been playing around with reducing error handling boilerplate You're not alone. Hundreds of us went into such thinking in the first weeks of reading/using Go - yet before we noticed how much more productive we are with Go's "boilerplate" than we were in languages where handling errors (failures) was "a problem of others", including future-us as "others". Perceived consensus of the Go community is that "error handling boilerplate" is a strong feature. I.e. in normal production software you MUST handle failures and you should do it as close as possible to the source of said failure. Go helps with that. Even team's proposal was finally retracted: https://github.com/golang/go/issues/32437 Discussion there is lengthy, but worth reading to sense why wider community considers "boilerplate" as asset. Error handling proposals umbrella: https://github.com/golang/go/issues/40432 > Michael. Hope this helps, -- Wojciech S. Czarnecki << ^oo^ >> OHIR-RIPE -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/20210214171250.4377c454%40xmint.
