Rust borrow checker

Two unsoundness bugs that have existed in the Rust borrow checker for roughly 11 years have been reported and filed in the Rust compiler's issue tracker on GitHub. The bugs allow code to bypass Rust's memory-safety guarantees, undermining the language's core promise. The discovery has drawn attention from the programming community, with discussion focusing on how long such issues can survive in a language built around safety.

Long-standing soundness holes in Rust's borrow checker have surfaced in a GitHub issue filed against the rust-lang/rust repository, apparently present in the language for around eleven years. The report is drawing attention on developer forums, with commenters debating how the bugs survived so long and what they mean for Rust's memory-safety guarantees.

A developer has published a proposal for a next-generation borrow checker designed to work as a drop-in replacement for Rust's existing borrow checking. The idea is generating discussion among Rust programmers, who are weighing whether the approach could ease well-known frustrations with the language's strict ownership rules while keeping its safety guarantees intact.