3 ms·
Similar to how Rust clearly is not memory safe, Go is also not memory safe.
by winterlights 11mo ago
Similar to how Rust clearly is not memory safe, Go is also not memory safe.
- vlovich123 11mo agoNot sure what this is saying but you can create a trivial concurrent program that violates the memory safety guarantees Go is supposed to provide [1]: https://biggo.com/news/202507251923_Go_Memory_Safety_Debate https://biggo.com/news/202507251923_Go_Memory_Safety_Debate That is not true of Rust.
- quotemstr 11mo ago> [You can] create a trivial concurrent [Go] program that violates the memory safety guarantees ... > That is not true of Rust. It's not supposed to be, but Rust does have plenty of outstanding soundness bugs: https://github.com/rust-lang/rust/issues?q=state%3Aopen%20label%3A%22I-unsound%22 https://github.com/rust-lang/rust/issues?q=state%3Aopen%20la... Rust as intended is safe and sound unless you write u-n-s-a-f-e, but as implemented has a ways to go.