@[email protected] to [email protected] • 14 hours agoI shouldve just learnt Go I'm getting clowned on by the fucking ai I'm gonna diediscuss.onlineimagemessage-square13fedilinkarrow-up168arrow-down120
arrow-up148arrow-down1imageI shouldve just learnt Go I'm getting clowned on by the fucking ai I'm gonna diediscuss.online@[email protected] to [email protected] • 14 hours agomessage-square13fedilink
minus-square@[email protected]linkfedilink5•5 hours ago It is similar to old error codes, but I feel that this makes one always have to be mindful of error handling and the non happy path Technically you need a separate linter (errcheck) to ensure you don’t just ignore errors. This is…not great. (That should have been a compiler error.)
minus-square@[email protected]linkfedilink2•5 hours agoYes, true. Having it built in in the compilation would be nice. Or at least having errcheck as a tool which already comes packed with Go. Go has changed over time to include more things like this. Maybe one day this will be addressed.
minus-square@[email protected]linkfedilink2•3 hours agoYeah, I was particularly glad to see the change in loop variable semantics become a stable part of the language. That was a terrible footgun. There are other things I dislike about Go, but I do think it’s improving while maintaining its better qualities, which is no small feat.
Technically you need a separate linter (
errcheck) to ensure you don’t just ignore errors. This is…not great. (That should have been a compiler error.)Yes, true. Having it built in in the compilation would be nice. Or at least having errcheck as a tool which already comes packed with Go.
Go has changed over time to include more things like this. Maybe one day this will be addressed.
Yeah, I was particularly glad to see the change in loop variable semantics become a stable part of the language. That was a terrible footgun.
There are other things I dislike about Go, but I do think it’s improving while maintaining its better qualities, which is no small feat.