Rust–: Rust without the borrow checker

Rust— (aka Rust without the borrow checker) just dropped a wild fork that yanks out Rust’s safety referee, letting code that normally gets blocked sail through. In plain English: it’s Rust without seatbelts, so you can reuse moved strings, grab multiple “do-not-touch” handles, and print the same thing twice without the usual “stop” signs. The dev crowd lit up. One camp cheered the chaos, cracking memes like “C++ with extra steps?” while others clutched pearls: “this looks memory-unsafe,” they warned, noting the original checker exists to prevent hard-to-find bugs and crashes. Practical folks asked the only question that matters: is it faster to compile? Meanwhile, a voice of reason begged for a “why” section in the readme, because without motivation it feels like a dare.

The thread turned meta fast, with predictions of angry comment marathons and “I can’t believe you shipped this” pile-ons. Some see a sandbox for experiments, teaching, or prototyping; others see a disaster waiting to happen if anyone uses it in real apps. The vibes: curiosity, comedy, and concern—equal parts “hold my beer” and “please don’t put this in production.” You can peek the fork on GitHub and decide which camp you’re in.