Re:Golang Diaries II
by ballard on Tuesday July 16, 2013 @12:51AM
(#6050093)
Yep. Sometimes crashing isn't an option. There are places in network & systems code that have seemingly complicated but darn important many permutations of state that already exist. Sometimes the differentiation between error conditions requires a combination of conditions (i.e., talking to an existing legacy system.)
As for single-threaded map, there are at least two necessary behaviors that handle errors very differently:
1. batch all errors/exceptions/etc and return them as an array
2. return on first error
As for single-threaded map, there are at least two necessary behaviors that handle errors very differently:
1. batch all errors/exceptions/etc and return them as an array 2. return on first error