you_can::turn_off_the_borrow_checker

Even more unsafe rust, great!

Cool idea. I was expecting more than just turn_off_the_borrow_checker in you_can though.

Maybe with time, as more counterexamples are needed for things "you can't just..." in rust.

I usually just box it and then Box::into_raw when I need multiple mutable references in a singlethreaded application where there's no deallocation or cleanup has to occur post shutdown.

though said for education purpose, keep finding these boundary-pushings playful. I can recall early days arrested by "several ways to access private members in C++" lol

This reminds me of Perl's ACME modules and I'm here for that.

Macros can secretly add "unsafe" blocks into the code?

Disgusting. I love it.