May 25, 2026
Safety called in sick
you_can::turn_off_the_borrow_checker
Rust fans are cheering, cringing, and joking as a tiny tool tells the safety rules to take a hike
TLDR: A new Rust macro can sidestep the language’s built-in safety checks, though its creator warns it’s only for learning and can cause dangerous breakage. Commenters were split between horrified admiration, prank-project nostalgia, and alarm over how easily code can hide risky behavior.
A cheeky new Rust macro has entered the chat, and the reaction is basically half horror movie, half standing ovation. The tool does exactly what its outrageous name promises: it can hush Rust’s famous safety guardrails so code that would normally be blocked can slip through anyway. The creator is practically waving red flags in all caps — this is for education, not real-world use, and it can make programs fail in weird, dangerous ways. Naturally, the community responded the only way the internet knows how: by turning the whole thing into a spectacle.
The loudest mood was a mix of disgust and delight. One commenter perfectly captured the vibe with the instant-classic line, “Disgusting. I love it.” That pretty much became the unofficial slogan of the thread. Another person said it felt like one of those old-school joke projects built purely to cause chaos and laughter, comparing it to Perl’s infamous prank-style modules. In other words: yes, it’s cursed, and yes, people are absolutely entertained.
But there was also genuine side-eye. One of the sharper reactions was basically, wait, macros can secretly inject unsafe code now? That sparked the real tension underneath the laughs: some readers saw this as a funny boundary-pushing stunt, while others saw it as exactly the kind of trick that makes safety-minded developers break into a cold sweat. A few veterans chimed in with their own sketchy workarounds from past experience, which only added to the "crime stories from programming’s wild side" energy. The result is a classic tech drama: a toy nobody should use, and a comment section that cannot stop staring at it.
Key Points
- •The article introduces a Rust macro, `you_can::turn_off_the_borrow_checker`, that suppresses many borrow-checker errors in annotated code.
- •It explicitly warns that the macro is unsafe, educational-only, and can enable unsound behavior that fails unpredictably and dangerously.
- •The macro works by rewriting explicit references created with `&`, `&mut`, `ref`, and `ref mut` to use an unsafe `borrow_unchecked()` helper.
- •An example shows code with multiple mutable borrows and a dropped owner becoming compilable once the macro is applied.
- •The approach has limits: it does not handle all lifetime-related errors or implicitly created references, though `&*` can sometimes force explicit references that the macro can rewrite.