Re:Why I’m not leaving Python for Go
by stcredzero on Monday September 24, 2012 @03:43AM
(#4563630)
> Error codes that need checking and aborting by hand at every function call boundary are a poor fit for replacing exceptions, because they optimize for the case where the error can be handled, rather than the usual case for exceptions, where the error cannot be handled.
From what I understand, the Go language team wanted to write robust servers, thus they wanted to "optimize for the case where the error can be handled."
From what I understand, the Go language team wanted to write robust servers, thus they wanted to "optimize for the case where the error can be handled."