As a participant on both sides of the discussion (pkg/errors and 
go-kit/log) I want to thank you for taking the time to put this package 
together, (with a great README file!!!) and present it to the community. I 
will definitely carve out some time to check it out and provide feedback.


On Tuesday, October 11, 2016 at 11:34:48 PM UTC-4, John Jeffery wrote:
> I have been following the progress of package, and 
> have put it to much use. Thanks very much to Dave Cheney and the other 
> authors.
> A few months ago an interesting issue was raised along the lines of being 
> able to attach arbitrary data to the error (
> Some interesting discussion 
> ensued, and in the end Dave decided not to add this feature to the package, 
> and gave some very good reasons for his decision. This is all good and I 
> think I learned a lot from the discussion.
> All the same I became quite interested in the idea that, if key/value 
> pairs of information could be attached to errors as they "bubble up" the 
> stack, then this could provide an alternative to passing a logger down 
> through the call stack, adding context along the way until something 
> actually has to be logged.
> So given that the package was not going to include 
> the feature, I decided to have a go at building an errors package that 
> provides a minimal API for programs that make use of structured logging. 
> The result is at The API has a very 
> small surface area, and I have found it pleasant to use in my own projects.
> Of course there are many other popular error handling packages, and 
> combines the best ideas of many of them. I think it 
> is a stated goal that be considered for inclusion 
> in the standard library at some point. I just have not seen structured 
> key/values integrated into error handling in quite the same way before, and 
> thought I'd mention this work and ask for community feedback.

You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to