News for hackers. Stuff that matters.

A comment on Errors in Go: From denial to acceptance. Parent comment

Re:Errors in Go: From denial to acceptance by dwaite on Monday November 26, 2018 @02:45PM (#18536209)
I believe what you are saying is that you can ignore errors if you check or rely on the side effects of an error (such as the result of a function being null on error).

One could argue that the side effect is part of the error, and really what you are ignoring are the details of an error (e.g. did the config entry fail to load because the config file wasn't found, because of filesystem permissions, or because the particular configuration key wasn't present?)

[ Parent | on HN ]
Re:Errors in Go: From denial to acceptance by sephware on Monday November 26, 2018 @02:52PM (#18536239)
That's a good way to put it, and yeah I would agree that's how I like to use errors: give me the details I ask for and let me ignore the ones I don't care about. Sometimes an "error" isn't really an error, and at those times exceptions are overkill. Sometimes an error really is an error and I need to let the user know something went wrong, give them enough details to let them fix it and wait for them to try again.
[ Parent | on HN ]