News for hackers. Stuff that matters.
Re:Go best practices, six years in by jud_white on Sunday May 01, 2016 @08:16PM (#11608499)
> having no stack for errors is insanely frustrating.

Check out https://github.com/pkg/errors

If you want more rich control of the output of the stack trace there's https://github.com/go-stack/stack

Re:Go best practices, six years in by dalyons on Sunday May 01, 2016 @08:55PM (#11608603)
Yeah, we've started using that. Kind of amazing that you need an addon lib & Wrap() everywhere to make errors useful. Just more boilerplate! :)