errors VS 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.

I have errors too ) https://github.com/nikandfor/errors

Full code with few tests is here

I did the same :)

I have errors package too.

I want to add that when wrapping error you should add function name you've called not function name you are in. Caller of your function already knows what he is called and he'll wrap it if he needs to. Or even better use human message and function name you can get out of Program Counter attached to the error. Non-stdlib errors package can do that (I use my own).

By the way I've experimented with errors either.