> No it really doesn't. It litters your code with if statements that are all just about the same, except that one that needs to be different, and you go blind looking at them all and can't spot the difference.
If most of your error handling is just bubbling the error up, you are doing something wrong.
if err != nil { return err; }
is an antipattern. Not because it's verbose, but because you are supposed to handle the error, not pass it right through, in most cases.
If most of your error handling is just bubbling the error up, you are doing something wrong.
is an antipattern. Not because it's verbose, but because you are supposed to handle the error, not pass it right through, in most cases.