I have accidentally failed to handle errors in golang code in a large corporate setting that was run under multiple linters. This was "simple" and straightforward code, and the last time it happened was within the past month. I wish I remembered exactly what I did, but it was rebased over to be fixed.
If you need sufficiently advanced linters to catch every case, your error handling is not explicit. Especially if those linters are not currently sufficiently advanced.
Re:Get familiar with workspaces
by throwaway894345 on Tuesday April 12, 2022 @04:24PM
(#31007807)
> If you need sufficiently advanced linters to catch every case, your error handling is not explicit.
You're conflating "explicit" and "statically verified".
Agreed that static verification by default is ideal. Rust wins here.
If you're writing alone in a vacuum without linters, then I agree that Rust is more explicit.