3 ms·
we know how to write Rust code that is guaranteed to be free from common classes of bugs that these No we don't. You are trying to shift the sands, by saying
by b112 5y ago
we know how to write Rust code that is guaranteed to be free from common classes of bugs that these
No we don't.
You are trying to shift the sands, by saying "But.. this one thing we can do...", except even that isn't true.
If we did, it wouldn't keep happening, year after year, decade after decade.
But even with peer reviews, with people supposedly knowing how, well.. it just keeps happening.
Do you think every occurrence is random chance? Or is it, maybe, just maybe, that humans can't write bug free code?
- vbphprubyjsgo 5y ago
- roca 5y agoIn practice safe Rust code never causes use-after-free bugs, for example, and UAF bugs are large fraction of exploitable RCE bugs. Safe Rust code could trigger a compiler bug that leads to use-after-free, or trigger a bug unsafe Rust code (i.e., code explicitly marked "unsafe") that leads to use-after-free; the latter are rare, and the former are even rarer. In practice I've been writing Rust code full time for six years and encountered the latter exactly once, and the former never. In either case the bug would not be in the safe code I wrote. I'm certainly not claiming that humans can write bug-free code. The claim is that with the right languages you can, in practice, eliminate certain important classes of bugs.
- b112 5y agoCan you now? So there will be no human error? And rust will have zero compile time bugs, ever? I'm not against improvement, but the absurd assumption that anything is safe. Because nothing is.
- littlestymaar 5y agoI guess kind of nihilist conservatism (“why bother changing anything since there's nothing we can do”) may explain why we are in such a bad situation today…