My thinking is part of the discussion in
https://commandcenter.blogspot.com/2017/12/error-handling-in-upspin.html
-rob
On Tue, Aug 7, 2018 at 7:43 AM, 'Axel Wagner' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> The message from an `error` is not for consumption by a developer, trying
The message from an `error` is not for consumption by a developer, trying
to find a bug in their program, but for consumption by a user/operator,
trying to find out what caused a failure. They may seem similar use-cases,
but in general, the latter finds stack traces incredibly useless and
frustrati
Such traces can be extremely useful for debugging an error caused deep inside
some library. Does Go opt not to do this by default in the errors package
because of the performance implications?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
