3 ms·
It's fine https://github.com/model-checking/verify-rust-std/issues/283 https://github.com/model-checking/verify-rust-std/issues/283 https://github.com/model-che
by zozbot234 1y ago
It's fine https://github.com/model-checking/verify-rust-std/issues/283 https://github.com/model-checking/verify-rust-std/issues/283 https://github.com/model-checking/verify-rust-std/pull/481 https://github.com/model-checking/verify-rust-std/pull/481 (But until two weeks ago, it wasn't - you could in theory cause UB by writing purely safe code within the Vec<T> implementation.)
- johnisgood 1y agoI had no idea, that is wild, especially considering how everyone has been outcrying "Rust is safe". Thanks for the info though. One should wonder what else is there... but they do not wonder, they are sadly rigid with their thinking that Rust is the perfect memory safe language with zero runtime overhead.
- Klonoar 1y agoYou know you can discuss languages without the weird emotional labeling from your last paragraph, right? Plenty of people wonder. It’s part of building the language.
- johnisgood 1y agoFair enough.
- zozbot234 1y agoIt's not real unsoundness because it only applies within the private implementation details of Vec<T> - you still can't cause UB from outside code. But it's a real oversight that only proves how hard writing unsafe code is.