> having no stack for errors is insanely frustrating. Check out https://github.c... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

jud_white on May 2, 2016 | parent | context | favorite | on: Go best practices, six years in

> 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

dalyons on May 2, 2016 [–]

Yeah, we've started using that. Kind of amazing that you need an addon lib & Wrap() everywhere to make errors useful. Just more boilerplate! :)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact