3 ms·
> Go forces to think about every error. Unless you just always return it up the chain without thinking about it like the bulk of the code I've encountered. No
by majormajor 3y ago
> Go forces to think about every error.
Unless you just always return it up the chain without thinking about it like the bulk of the code I've encountered. No more thoughtful than "catch and reraise" or "just throw."
And like in Java, an NPE ain't getting caught by the error return of a function in Go either.
- masklinn 3y agoEven if you ignore this, assume nobody ever created an editor macro to smash, go has several glaring holes which make it very possible (and reasonably easy) to miss errors entirely. And unlike Java, those errors are just gone, they won’t be breaking noisily eventually.