Re:Implications of Rewriting a Browser Component in Rust
by masklinn on Thursday February 28, 2019 @12:50PM
(#19273317)
> This is like saying the Rust doesn't have memory safety because you can use "unsafe".
It's the exact opposite which is the point. Rust requires extra work and using the non-default and less convenient way for unsafety, C++ requires extra work and using the non-default method and less convenient way for safety.
It's the exact opposite which is the point. Rust requires extra work and using the non-default and less convenient way for unsafety, C++ requires extra work and using the non-default method and less convenient way for safety.