>>178
Exceptions (or similar constructs using jmp operators) are necessary to build reliable software.
Untrue. You can as easily write reliable software with alternate error handling and Go's error return parameters do the job well. In fact, they even get rid of a common ``feature'' that actually makes exceptions
less reliable: your programs will no longer abort just because you've forgotten to handle whichever exception something may throw. Exceptions introduce problems of their own and are not nearly the best and ultimate way to handle errors.
They are often more efficient than the alternatives, like passing around error codes
Haha, you're funny. Please, do tell me how exactly is stack unwinding more efficient than, say,
errno or returning a value?
to which Go does not offer anything else.
Another piece of disinformation. Go offers the
panic/
recover mechanism, which is basically what your exceptions are. However, you shouldn't use it for standard errors, only for truly catastrophic failures that make the continuation of this program (at least this piece of it) impossible.