Re:Why Go Is Not Good (2014)
by fenollp on Thursday December 10, 2015 @04:36AM
(#10709749)
This is exactly the pattern that Erlang handles the best:
1. Expect you call to os.Open to not fail
2. Then do stuff with it
2bis. Or the running process will crash, the error logged, bad state won't mess up the flow and a dev can always hot-patch it
1. Expect you call to os.Open to not fail 2. Then do stuff with it 2bis. Or the running process will crash, the error logged, bad state won't mess up the flow and a dev can always hot-patch it