janAkali@lemmy.sdf.org to Programmer Humor@programming.dev · 3 days agoUnsafe Rust: living up to its namelemmy.sdf.orgimagemessage-square11fedilinkarrow-up153arrow-down164
arrow-up1-11arrow-down1imageUnsafe Rust: living up to its namelemmy.sdf.orgjanAkali@lemmy.sdf.org to Programmer Humor@programming.dev · 3 days agomessage-square11fedilink
minus-squaretyler@programming.devlinkfedilinkarrow-up86·3 days agoIt’s not. It’s literally code in an unsafe block. The OP is either trolling or actually ignorant.
minus-squarejanAkali@lemmy.sdf.orgOPlinkfedilinkarrow-up8arrow-down33·3 days agohttps://doc.rust-lang.org/nomicon/races.html Safe Rust guarantees an absence of data races I know that it was unsafe block in this CVE, but the irony of the situation is funny.
minus-squarexylogx@lemmy.worldlinkfedilinkEnglisharrow-up65arrow-down1·3 days agoNot only unironic but explained in the doc you referenced: “However Rust does not prevent general race conditions. This is mathematically impossible in situations where you do not control the scheduler, which is true for the normal OS environment.”
It’s not. It’s literally code in an
unsafeblock. The OP is either trolling or actually ignorant.https://doc.rust-lang.org/nomicon/races.html
I know that it was unsafe block in this CVE, but the irony of the situation is funny.
Not only unironic but explained in the doc you referenced:
“However Rust does not prevent general race conditions.
This is mathematically impossible in situations where you do not control the scheduler, which is true for the normal OS environment.”