3 ms·
It also prevents adding relevant context to the errors, meaning you get all the joy of hunting through call stacks to figure out what went wrong in a sufficient
by badrequest 3y ago
It also prevents adding relevant context to the errors, meaning you get all the joy of hunting through call stacks to figure out what went wrong in a sufficiently complex program.
- t0astbread 3y agoWhen I write tooling for myself in Go, I usually wrap all of my errors with stacktraces since I hate having to grep for a string that may be interpolated or duplicated throughout the codebase. Addendum: It is still a good thing to be able to add context to the error message though, so I think you've got a point.