> > > Languages like Go make it too easy to ignore errors. > > What? I've almost exclusively heard the opposite: Go makes error handling too in-your-face. Peop

> > > Languages like Go make it too easy to ignore errors. > > What? I've almost exclusively heard the opposite: Go makes error handling too in-your-face. People don't like writing "if err != nil" constantly. > Do you actually have to look at the value you err, or can you just pretend like it's not there? (genuinely asking, I thought it was the latter). While Go may not have all the capabilities Rust has at forcing error inspection, it really isn't in the class of languages that "make it too easy to ignore errors". I agree that a lot of it is convention, but multi-value returns, usage of named variables and good practices in the base libs (flowing upwards) can't place it in the realm of easily ignoring errors.