Re:Twelve Go Best Practices
by alco on Wednesday July 31, 2013 @06:47PM
(#6137323)
You can panic inside Write() and recover at the top of the DumpBinary() function. This has been demonstrated by Rob Pike and Andrew Gerrand in a talk at Google IO.
As long as you don't leak panics outside of your package, it's OK to use them for non-local error returns.
Re:Twelve Go Best Practices
by Someone on Thursday August 01, 2013 @03:20AM
(#6139083)
Yes, but that would work best if the culture was to panic to signal errors. If it is not (as IIRC in go), you need to wrap common library calls to do so.
As long as you don't leak panics outside of your package, it's OK to use them for non-local error returns.