It remains to be seen whether that approach will guarantee memory safety. Last I checked, it had gaping soundness holes related to aliasing. (Note: most of the complexity and innovation in Rust is about controlling aliasing.)<p>When all the soundness holes are closed, then we&#x27;ll have to evaluate whether it&#x27;s usable to program in. At the very least, Rust is years ahead here.<p>Even if those hold up, you have to consider whether rewriting your C++ code to fit the safe subset is actually worthwhile, compared to rewriting in Rust which gives you additional benefits.