Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

While I agree that Rust got it right by being more explicit, a lot of bugs in C/C++ can also easily avoided with good engineering practices. The Rust argument that it is mainly the fault of the programming language with C/C++ was always a huge and unfair exaggeration. Now with this entirely predictable ".unwrap" desaster (in general, not necessarily this exact scenarious), the "no true Rustacean would have put unwrap in production" fallacy is sad and funny at the same time.


Unwrap is controversial. The problem is that if you remove it, it makes the bar even higher for newcomers to Rust. One solution is to make it unsafe (along with panic).


> the "no true Rustacean would have put unwrap in production"

The "no unwrap" rule is common in most production codebases. Chill.


Could you point one that is Open source?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: