2 ms·
>That's bad Go design. I think that's the parent's point. Though, not that that is bad Go API design on behalf of the library authors (as you imply), but that
by coldtea 7y ago
>That's bad Go design.
I think that's the parent's point.
Though, not that that is bad Go API design on behalf of the library authors (as you imply), but that that is a sign of Go's own bad design -- the fact that it leaves it to programmers own devices to get their API design right with respect to errors...