Hacker News Reader

You've misunderstood what this library does. You do not need a third-party package to reliably get error stacks. You can get stack traces from any point in a program --- for errors, or for performance monitoring, or anything else --- any time you want in Go, which is probably the reason they're not attached to errors by default.

Go errors are not exceptions.

View on HN

A stack trace is not an error stack. The GP was lamenting the fact that a 3rd party package is required to create error stacks, not stack traces.

Out of curiosity: what's the difference between an error stack and a stack trace?

I'm unclear on whether they mean "errors with stack traces attached" (trivially available) or "errors that are stacks of errors" (requires small third party library".

If the latter: fair enough, but it's not as if that's a common feature of other mainstream languages.

Reply on news.ycombinator.com