@smari @yaelwrites It never appeared like that to me - the Rust approach is that as long as the code is not `unsafe`, Rust statically guarantees:
- No data races (Send/Sync)
- No use after free
- No unsafe pointers of any kind
basically https://en.wikipedia.org/wiki/Rust_(programming_language)#Memory_safety
@monad_cat @yaelwrites to be clear, I'm not hating on Rust. I'm just being (perhaps excessively) formalistic because it's such a big claim.
That said, I don't really enjoy using it - because the enforcement of these safety measures isn't done by the compiler, but by the programmer by being forced to jump through inane semantic hurdles. 😅
I do, to the point that coding python feels wrong, or like cheating. I'm not exactly doing it for a living, but I do genuinely enjoy coding in rust.