On Mon, Apr 24, 2017 at 6:31 PM, Dan Kortschak <dan.kortsc...@adelaide.edu.au> wrote: > 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.
Also a great example! The main take away here is that we should always design for failure, and sometimes the primary failure mode should be "abort at all costs and let the application developer know that something catastrophic happened which could lead to worse things happening in the future". —Sam -- 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.
