logutil VS errors

> At boundaries between our code and calls out to external packages, make an effort to always wrap the result with xerrors.Errorf. This ensures that we always capture a stack trace at the most proximate location of an error being generated as possible

I've been doing something similar for a while using `errors.WithStack` from https://github.com/pkg/errors

The error can then be logged with https://github.com/rs/zerolog like this `log.Error().Stack().Err(err).Msg("")`

And using a console writer it's possible to get human readable output instead of the standard JSON, see https://github.com/mozey/logutil

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.