4 ms·
You shouldn't, and I write Rust all the time. Don't implicitly trust it because it's written in Rust. There could still be errors, there could be uses of unsafe
by leshow 8y ago
You shouldn't, and I write Rust all the time. Don't implicitly trust it because it's written in Rust. There could still be errors, there could be uses of unsafe, etc.
- pests 8y agoI just said more than C not an absolute trust level or trust just because it's Rust. I do know Rust very well myself. It does have some gotchas for those who think it means instant safety. For example the interface between safe and unsafe. If you change an established constraint that safe Rust depends on inside an unsafe block then all safe code has to be aware of this change and take it into account. In a way anything could be undefined behavior if you don't. Or the hole that allowed RAII guard subversion.
- leshow 8y ago> Or the hole that allowed RAII guard subversion. ?