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 frustrating. If I run your software and I have to read your source code to figure out what mistake I made configuring it (or something like that), I will uninstall it immediately.
If you need a stack trace for debugging, you can always get one via https://godoc.org/runtime/debug#PrintStack On Mon, Aug 6, 2018 at 11:34 PM 'Anmol Sethi' via golang-nuts < golang-nuts@googlegroups.com> wrote: > 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 unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
