you_can::turn_off_the_borrow_checker

Arbitrary mention: Crust[0]

[0] https://github.com/tsoding/crust

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.

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

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.

I wonder if this has any measurable impact on compile times.

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

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

Even more unsafe rust, great!

Disgusting. I love it.