News for hackers. Stuff that matters.
Re:11 year old unsoundness bugs found in Rust borrow checker by vrighter on Tuesday October 13, 2026 @09:55AM (#50071821)
so why put them in before knowing if they work reliably? That's the YOLO part, to me
Re:11 year old unsoundness bugs found in Rust borrow checker by cscheid on Tuesday October 13, 2026 @10:44AM (#50072550)
The same combination of reasons we've been doing these kinds of heuristic implementations forever:

- people still get value off of an incomplete implementation, because we are allowed to be mindful of the issues (see, eg, UB in C++). In other words, many, many more bugs have been prevented by the borrow checker working as intended than have been caused by it working poorly. It's not particularly close.

- theory almost always moves slower than practice

The mutable state situation pointed out by the grandparent poster was a famous issue in typing SML under mutability that required serious changes in the language, see Section 4.2 here: https://smlfamily.github.io/history/SML-history.pdf

These were Turing-award caliber people figuring it out and, according to your definition, "yolo"ed it. This stuff is _hard_, and these driveby comments truly aren't helpful.

Re:11 year old unsoundness bugs found in Rust borrow checker by vlovich123 on Tuesday October 13, 2026 @10:46AM (#50072585)
Because there’s real value delivered even before that? Perfect bring the enemy of good and all that
Re:11 year old unsoundness bugs found in Rust borrow checker by dwattttt on Tuesday October 13, 2026 @10:43AM (#50072547)
You're claiming that this bug that reproduces back to Rust 1.4 (2015) is a sign they're adding too many features to make sure they don't introduce bugs? Or do you have bugs that are due to these recent features?