It has been almost two years since this post:
https://dave.cheney.net/2016/06/12/stack-traces-and-the-errors-package

What is current best practice? Should I use some package to gift wrap 
errors in order to get stack trace attached to them?

Standard library errors package is really "bare bones". Some guidance would 
be appreciated.

-- 
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 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to