errors
Go stdlib errors package extension. (by tlog-dev)
errors
errors with stacktraces for go (by go-errors)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of errors.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-15.
-
Share Your Code.. Share your most unique piece of Go code.
I have errors too ) https://github.com/nikandfor/errors
-
Proposal: errors.With(err, other error) error
Full code with few tests is here
-
Anyone using github.com/pkg/errors for stack traces?
I did the same :)
-
go-faster/errors: clear go error wrapping with caller (xerrors fork with Wrap)
I have errors package too.
-
Effective Error Handling in Golang
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).
-
e4: an error handling package
By the way I've experimented with errors either.
errors
Posts with mentions or reviews of errors.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-07.
- Error handling and serializing
-
Anyone using github.com/pkg/errors for stack traces?
Is anyone using this package? Is it dead? If not, is there another good package or approach for generating stack traces for errors that you've found and liked? I've seen github.com/go-errors/errors which offers simple stack traces but does not seem to have great adoption. I feel like there must be a popular solution for this, besides rolling your own stack trace functions with the runtime lib.
-
Transitioning from Java to GoLang
take a look at this for examples: https://github.com/go-errors/errors
What are some alternatives?
When comparing errors and errors you can also consider the following projects:
errors - A drop-in replacement for Go errors, with some added sugar! Unwrap user-friendly messages, HTTP status code, easy wrapping with multiple error types.
simplerr - Advanced Go error handling, made simple
errors - Go error library with error portability over the network
blockscan - a mini blockchain scanner
errors - Simple error handling primitives
pcre - Pure-Go port of the PCRE2 regular expression engine.
go - The Go programming language
snaky - snake game implementation using 2d array in Go
resperr - Go package to associate status codes and messages with errors