FRESH

Hacker News

you_can::turn_off_the_borrow_checker

54 points by striking

by tempesttempo86

1 subcomments

by wasmperson

0 subcomment

Rust's memory safety is as much a social convention as it is a language feature. The language has something better described as "mutation safety," and it's the job of library developers to use that to design UB-free APIs.
I think many people understand this subconsciously, and that this is what drives some of the more performative security culture in Rust spaces (superfluous safety comments, shunning of certain crate authors, `forbid(unsafe)`, push-back against syntax sugar, etc.).

by EFLKumo

1 subcomments

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

by extraduder_ire

0 subcomment

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.

by space_ghost

1 subcomments

by himata4113

0 subcomment

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.

0 subcomment

by codedokode

3 subcomments

by Pesthuf

0 subcomment

by rurban

0 subcomment

by orphea

0 subcomment