文件列表:

.golangci.yml (2908, 2021-09-01)
LICENSE (1073, 2021-09-01)
Makefile (366, 2021-09-01)
annotation.go (331, 2021-09-01)
annotation_test.go (1302, 2021-09-01)
caller-fixtures_test.go (291, 2021-09-01)
caller.go (524, 2021-09-01)
caller_test.go (638, 2021-09-01)
example_1_test.go (639, 2021-09-01)
example_2_test.go (752, 2021-09-01)
example_3_test.go (799, 2021-09-01)
examples_test.go (1200, 2021-09-01)
go.mod (244, 2021-09-01)
go.sum (1615, 2021-09-01)
images (0, 2021-09-01)
images\github_com_dc0d_wrapperr.png (232137, 2021-09-01)
images\github_com_dc0d_wrapperr_annotate.png (240470, 2021-09-01)
loc.go (295, 2021-09-01)
loc_test.go (712, 2021-09-01)
stack.go (3183, 2021-09-01)
stack_fixtures2_test.go (861, 2021-09-01)
stack_fixtures_test.go (873, 2021-09-01)
stack_test.go (6386, 2021-09-01)
test-watch.sh (85, 2021-09-01)
wrapperr.go (132, 2021-09-01)
wrapperr_test.go (223, 2021-09-01)

[](https://pkg.go.dev/github.com/dc0d/wrapperr) [](https://goreportcard.com/report/github.com/dc0d/wrapperr) [](https://codeclimate.com/github/dc0d/wrapperr/maintainability) [](https://codeclimate.com/github/dc0d/wrapperr/test_coverage) # wrapperr _Where_ did that error happen down the call chain? > Right at the bottom!
All you need to do is, instead of: ```go return nil, err ``` Do: ```go return nil, wrapperr.WithStack(err) ``` Also, it is possible to annotate the stack in the middle:
And to get the original error, just used the standard `errors.Unwrap(error)` function from built-in `errors` package.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：