APIs, Return codes, C Programming Language, We've all been there.
TL;DR: Don't return codes to yourself. Raise Exceptions.
Pro...
For further actions, you may consider blocking this person and/or reporting abuse
Tell the designers of Go programming language.
There's no exception.
Error checking everywhere.
That's exactly the same thing that occured to me, at first. Except, in Go they call "them" Errors and they are the mechanism that serves the same purpose, implemented different way. In the same manner you probably shouldn't return error codes in Go, but return Error objects as the second return value.
Yes. That is why I would chose a more mature language and not one based on the 60s.
But if performance is the ONLY concern I think we can tolerate lots of code smells . It is a price to pay
if you read this sentence on the article above you will find your own answer
Avoid immature and premature optimized languages favoring return codes