errors VS backward-cpp

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.

I've used backward-cpp for printing stack traces and I'm very satisfied!

if you're just looking for a way to log the stack trace at the time, you can use: https://github.com/bombela/backward-cpp

100% Shameless plug. Stack capture and pretty printer for C++: https://github.com/bombela/backward-cpp

have you tried backward-cpp?: https://github.com/bombela/backward-cpp