>
>
> Wouldn't be great to have a "syntactical sugar" to make things (at least a
> little bit) simpler in our beloved Go language?
>
>>
>>
no, I don't think so.
Something that few in in this thread have focused on is the most important
part of the go error handling story happens *before* the `return err`
statement
if err != nil {
// this is the important part
return err // this is not
}
Specifically, when an error occurs, cleaning up the accumulated state to
that point, removing any temporary items like files on disk, transactions,
etc, so that the caller can attempt to retry the operation if they so
choose.
Now it happens that most times, thanks to things like defer, there is
usually nothing to handle in the cleanup phase before returning the error,
but in my opinion does not take anything away from this being the most
important part of Go's error handling story.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
