We (gonum) would extend the security exception to include scientific code; there are far too many peer reviewed works that depend on code that will blithely continue after an error condition that should stop execution or log failure. These can and do end up contributing to costs of (mis)development of pharmacuetical and other health-related technologies and worse in patient health outcome failures (also probably in other field, but I those are outside my expertise).
For horror, see this talk https://youtu.be/7gYIs7uYbMo?t=523 (time at point in talk where he talks about the software issues that ultimately resulted in drug trials based on completely spurious data). On Mon, 2017-04-24 at 08:41 -0500, Sam Whited wrote: > While I generally agree with you, panics in libraries should probably > not bubble up to anythihng outside of the library, the exception is > security issues. If for some reason I can't get a handle to > urandom(4) > I'd probably rather crash the program than risk having another > developer ignore that error and generate keys with a zeroed IV (or > whatever the case may be). -- 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.
