errors VS errors

Can you explain why we should this over https://github.com/pkg/errors?

The pkg/errors package offers some nice add-ons for easier error handling. Too bad it was put into maintenance mode pending whatever changes/improvements are coming in Go 2.

I can't figure out the issue so here for some help, I am using `neovim/nvim-lspconfig` my `gopls` doesn't recognise external paths such as `github.com/pkg/errors` , it throws error`could not import github.com/pkg/errors (cannot find package "github.com/pkg/errors" in any of /usr/local/go/src/github.com/pkg/errors (from $GOROOT) /Users/ra compiler (BrokenImport)\`

Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors

Should've been something like errors.Newf("failed to foofoo %s", foo) instead and preferably never invent %w but have some controlled way to wrap like errors.Wrapf(err, "failed to foofoo %s", foo) that was in ye olde github.com/pkg/errors.

Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.

Im using zerolog and in order to get the stack trace for my error I have to wrap my error in errors.Wrap from "github.com/pkg/errors".

And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)

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.