Re:DARPA: Translating All C to Rust (Tractor)
by commodoreboxer on Tuesday July 30, 2024 @12:23PM
(#41110909)
> This repository demonstrates that, when using 'safe' Rust, there are still double-digits cases where you may still encounter dread-pirate-UB.
No it doesn't. Miri is for unsafe code. There's no UB in safe Rust by design. Any UB caused without unsafe is considered a bug to be fixed.
Re:DARPA: Translating All C to Rust (Tractor)
by PreInternet01 on Tuesday July 30, 2024 @01:18PM
(#41111679)
MIRI also detects problems in generally safe Rust. If you want to know how I know, read the sibling comments. Or, like, just downvote me, it's not like I care about my imaginary Internet points.
The sanity of future devs, though? I do care about that, though, and there is a huge problem with that in the Rust 'community'
Re:DARPA: Translating All C to Rust (Tractor)
by nequo on Tuesday July 30, 2024 @01:42PM
(#41111992)
> ... in generally safe Rust.
Just to find agreement about the terminology, wouldn't we call all code that is not inside an unsafe block "safe?" If so, then adding "generally" is superfluous, right?
If not, then how is "generally safe" different from "not inside an unsafe block?"
I didn't expect you to outright confirm that you are using the "solve all programming problems ever" strawman, but, err, thanks for the proof I guess. I thought maybe I went a bit overboard in the reading between the lines but I guess I nailed it.
Again, I don't want to argue against you using or enjoying Rust, I would merely like to point out that it does, demonstrably, not solve all programming problems ever...