>> Relying on documentation is not a silver bullet either: poor documentation is still very much a thing. >> It makes sense always to check the documentation t

>> Relying on documentation is not a silver bullet either: poor documentation is still very much a thing. >> It makes sense always to check the documentation to find out whether an error type is a part of the function signature. O_o. So on the one hand you don't know if a function will throw an exception and can't rely on the docs, while on the other you don't know if it will return an error code so you should check the docs. I don't write Go yet, although I look at a fair bit of it. A friend of mine who works a lot in it tells me he was put off at first but basically decided to trust the language's idioms for now. Until I have more personal experience my outlook is: "man, I think I would really miss exception handling" with a smattering of "boy that sure looks more error prone to me."