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
Perhaps tangentially related: <a href="https://github.com/tsoding/crust" rel="nofollow">https://github.com/tsoding/crust</a>
Macros can secretly add "unsafe" blocks into the code?
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.
This reminds me of Perl's ACME modules and I'm here for that.
Disgusting. I love it.