Re:fork() can fail
by donatj on Wednesday August 20, 2014 @09:23PM
(#8205522)
Actually if you want to not handle an error, you have to do either _ = err or just go data, _ = doStuff(), both of which are very visible. You can basically scan your codebase for _'s and find all the unhanded exceptions. If you don't do something with a variable, eg I do myInt := 1 but I don't use myInt go simply refuses to compile.
[ Parent
| on HN ]
Technically true but most of the [admittededly modest] Go code I've seen had that error punt all over the place. I really wish they'd learned from C and either banned assigning _ for errors or threw a compiler error if the next line wasn't a _ check.
On second thought, it'd probably avoid some nasty production failures if that behaviour was true for everything which can return an error.