You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
forest 302dfe814a remove test files 4 years ago
.gitignore Initial commit 9 years ago
.travis.yml travis.yml: add Go 1.13 5 years ago
LICENSE LICENSE: remove trailing newline (#61) 8 years ago
Makefile Makefile: switch to staticcheck (#187) 6 years ago travis.yml: add Go 1.13 5 years ago
appveyor.yml add appveyor.yml (#36) 8 years ago
errors.go Revert "Support Go 1.13 error chains in `Cause` (#215)" (#220) 5 years ago
go113.go Revert "Support Go 1.13 error chains in `Cause` (#215)" (#220) 5 years ago
stack.go Add json.Marshaler support to the Frame type. (#197) 5 years ago

errors Travis-CI AppVeyor GoDoc Report card Sourcegraph

Package errors provides simple error handling primitives.

go get

The traditional error handling idiom in Go is roughly akin to

if err != nil {
        return err

which applied recursively up the call stack results in error reports without context or debugging information. The errors package allows programmers to add context to the failure path in their code in a way that does not destroy the original value of the error.

Adding context to an error

The errors.Wrap function returns a new error that adds context to the original error. For example

_, err := ioutil.ReadAll(r)
if err != nil {
        return errors.Wrap(err, "read failed")

Retrieving the cause of an error

Using errors.Wrap constructs a stack of errors, adding context to the preceding error. Depending on the nature of the error it may be necessary to reverse the operation of errors.Wrap to retrieve the original error for inspection. Any error value which implements this interface can be inspected by errors.Cause.

type causer interface {
        Cause() error

errors.Cause will recursively retrieve the topmost error which does not implement causer, which is assumed to be the original cause. For example:

switch err := errors.Cause(err).(type) {
case *MyError:
        // handle specifically
        // unknown error

Read the package documentation for more information.


With the upcoming Go2 error proposals this package is moving into maintenance mode. The roadmap for a 1.0 release is as follows:

  • 0.9. Remove pre Go 1.9 and Go 1.10 support, address outstanding pull requests (if possible)
  • 1.0. Final release.


Because of the Go2 errors changes, this package is not accepting proposals for new functionality. With that said, we welcome pull requests, bug fixes and issue reports.

Before sending a PR, please discuss your change by raising an issue.