errors

I found the https://github.com/juju/errors library to be a very practical way to include tracing info in the error values. I wish the core error library behaved like that, and that the core language made it less verbose. This is a typical thing in Go: the language is kept stable and backward compatibility is king. Solutions for some things are left to the community. Other languages changed a lot over the years, getting better but frustrating people because of breaking changes. I believe this promise of stability paved the way for much of Go's success, despite many shortcomings

Having been writing Go for 4 years now, I can say that Dave Cheney's package is exactly what I've been looking for. The thing that really sells it to me is the being able to wrap the error when necessary with errors.Wrap and find the underlying cause with errors.Cause. I've yet to experiment with the new formatting `%+v` but I can see that coming in useful too. There have been earlier attempts at something similar (eg https://github.com/juju/errors) but none with the same clarity of thought. So thanks for a great package Dave and for taking the time to whittle it down into the simplest, most elegant thing.