Simple error handling primitives
 
 
Go to file
Dave Cheney 1b876e063e Remove WithStack and WithMessage public functions
The refactoring to use withStack and withMessage types is useful enough
to land indepdently of exposing these helpers publically.
2016-08-08 14:39:38 +10:00
.gitignore Initial commit 2015-12-27 13:05:38 +01:00
.travis.yml update go 1.6 version 2016-05-23 17:46:48 +10:00
LICENSE LICENSE: remove trailing newline (#61) 2016-06-28 08:23:52 +10:00
README.md Documentation improvements (#69) 2016-07-19 19:13:40 +10:00
appveyor.yml add appveyor.yml (#36) 2016-06-07 07:41:47 +10:00
bench_test.go errors: add a benchmark comparing stack trace performance (#74) 2016-07-24 12:43:27 +10:00
errors.go Remove WithStack and WithMessage public functions 2016-08-08 14:39:38 +10:00
errors_test.go Remove Fprint (#47) 2016-06-10 11:53:11 +10:00
example_test.go Capitalise first letter of trace. (#60) 2016-06-27 12:13:31 +10:00
format_test.go Destructure Wrap{,f} into WithStack(WithMessage(err, msg)) 2016-08-08 14:31:22 +10:00
stack.go Destructure New/Errorf 2016-08-08 14:31:22 +10:00
stack_test.go Remove WithStack and WithMessage public functions 2016-08-08 14:39:38 +10:00

README.md

errors Travis-CI AppVeyor GoDoc Report card

Package errors provides simple error handling primitives.

go get github.com/pkg/errors

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
default:
        // unknown error
}

Read the package documentation for more information.

Contributing

We welcome pull requests, bug fixes and issue reports. With that said, the bar for adding new symbols to this package is intentionally set high.

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

Licence

BSD-2-Clause