3 ms·
I agree with everything you've written in this comment. I'd like to split a hair here and say, this is a "Go's standard library" problem, and not a "Go languag
by margalabargala 2y ago
I agree with everything you've written in this comment.
I'd like to split a hair here and say, this is a "Go's standard library" problem, and not a "Go language" problem.
Good API design for a software package should have proper error semantics.
Good API design for a language, allows for flexibility in actual implementation, alongside standards that say "you SHOULD do this".
- gf000 2y agoDisagree. This level of convention is inseparable from the language. Not doing the conventional error return in go would be akin to using a Return sum type in reverse, putting the success value into the Error case..
- deleted 2y ago[deleted]