errors
errors
| errors | errors | |
|---|---|---|
| 2 | 6 | |
| 60 | 1,979 | |
| - | 1.5% | |
| 3.2 | 5.1 | |
| 11 months ago | 9 days ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
errors
errors
-
Who returns specific error interfaces to model domain 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.
-
Go's Error Handling Is a Form of Storytelling
https://github.com/cockroachdb/errors has worked great for me! Agreed this should be part of the core language though.
-
Anyone using github.com/pkg/errors for stack traces?
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.
-
go-faster/errors: clear go error wrapping with caller (xerrors fork with Wrap)
The cockroachdb/errors is too big
- Error stack traces in Go with x/xerror
-
Comparison golang stacktrace error library output
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.
What are some alternatives?
eris - Error handling library with readable stack traces and flexible formatting support 🎆
golangci-lint - Fast linters Runner for Go
bugsnag - Well-documented, maintainable, idiomatic, opinionated, and *unofficial* rewrite of the Bugsnag Go notifier
emperror - The Emperor takes care of all errors personally
errors - Go stdlib errors package extension.
zerolog - Zero Allocation JSON Logger
go-ez - An experimental Go package that allows you to write less error handling and makes the logic look simpler and clearer.
errors - Simple error handling primitives
pears-go - harvest Go errors with ease
backward-cpp - A beautiful stack trace pretty printer for C++
errors - errors with stacktraces for go
json-logs - A tool to pretty-print JSON logs, like those from zap or logrus.