News for hackers. Stuff that matters.
Re:Declined Proposal: A built-in Go error check function, “try” by sagichmal on Wednesday July 17, 2019 @03:05PM (#20462917)
One distinction that is often made by core team members is that you only need to annotate errors at package boundaries, and that returning unannotated errors within a package is fine. But in most code, the packages are not so well-defined, or well-thought-out, or sacrosanct, that they represent a good proxy for annotation decisions.

I would much rather have an error with too much or duplicate annotation than one with not enough. And I would further argue that, yes, in the stdlib, errors are generally under-annotated.

There are no comments on this comment yet.