I suspect that the solution to unsafe languages like C/C++ will end being a small sanitizer runtime like CFI(<a href="https://dslab.epfl.ch/research/cpi/" rel="nofollow noreferrer">https://dslab.epfl.ch/research/cpi/</a>), that also supports some form of extended MTE, for memory safety.<p>For hot parts of the code that the sanitizer can guarantee is safe, either due to it being trivial or with annotations(<a href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p2771r0.html" rel="nofollow noreferrer">https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p27...</a>), it can safely exclude these checks to limit performance impact.<p>This seems much more realistic than e.g. Microsoft rewriting Excel in Rust with bug for bug compatibility. It would also benefit Rust code, that has sections marked as unsafe.