errors VS errors

Is anyone using this package? Is it dead? If not, is there another good package or approach for generating stack traces for errors that you've found and liked? I've seen github.com/go-errors/errors which offers simple stack traces but does not seem to have great adoption. I feel like there must be a popular solution for this, besides rolling your own stack trace functions with the runtime lib.

take a look at this for examples: https://github.com/go-errors/errors

I usually use https://github.com/cockroachdb/errors for reasons that you can read in their documentation. It is well thought out and is no more complicated than it needs to be. It is a drop in replacement for the standard errors package and they have built this from experience, which is usually a good thing. It is usually best to stick to interfaces. With concrete errors, you will be doomed to deal with them forever.

https://github.com/cockroachdb/errors has worked great for me! Agreed this should be part of the core language though.

https://github.com/cockroachdb/errors is the most featureful in this space, but is heavy if you don't need network portability, redaction, and all the other bells and whistles.

The cockroachdb/errors is too big

Golang is great. I mostly love it. However, collecting an error with relevant context and a nicely formatted stacktrace is kind of a mess of competing approaches. This this feature comparison is a good overview of the landscape.