News for hackers. Stuff that matters.
Re:Declined Proposal: A built-in Go error check function, “try” by mikeschinkel on Thursday July 18, 2019 @05:44PM (#20474207)
I would argue that if you are using boilerplate annotations, you are doing it wrong. If you really do not need to add context, don't add context. But in my code I find that I want to add context about 90% of the time.

But then I am super zealous about making sure my error messages understandable without the need to track down other information. For example, I want to know that (something like) "the config file needs group read permissions" not "file cannot be opened." But maybe others value ease of programming more than I do and are less concerned about error UX than I am?

There are no comments on this comment yet.