2 ms·
Violations to the C++ best practices that enforce memory safety are definitely visible during code reviews. The harder problem is convincing people that raisin
by mgaunard 5y ago
Violations to the C++ best practices that enforce memory safety are definitely visible during code reviews.
The harder problem is convincing people that raising their quality standards is a necessary requirement for them to contribute to the code.
- Cyph0n 5y agoFirstly, the difference I was trying to emphasize is "guaranteed to be visible due to the unsafe keyword" vs. "potentially not visible". Secondly, quality standards rely on the human element, which we know is fallible and never 100% reliable. Compiler-enforced memory safety checks are (in theory) infallible[1]. [1]: Infallible when all of your dependencies are also verifiably memory safe. In reality, this is not the case, but I believe that Rust can reliably get much closer to 100% than usual.