This comes from experience working on large golang code bases, with error linters, and seeing errors silently and unintentionally ignored.
If you mean that programmers caught the error and just made it "go away", convincing the checker that it was handled but in fact it was not, that's not something a language can solve. There is no amount of "forcing" a programmer to handle an error that they can't bypass.
For me it really stood out because thats when i first tried go, and while i found the error handling annoying, i found it rather directly addressed that issue.