They did, it’s called rustc. A compliant C compiler cannot escape giving a programmer unfettered access to manipulate memory, so the problem is not in the compiler. There are safe subsets of C that don’t exhibit these problems, but a compiler that only supports such a subset is no longer a C compiler.
Instead of mass translating C code in some insane ready-to-ruin codebases project, why not just… make a compiler that addresses the vulnerabilities?
They did, it’s called
rustc. A compliant C compiler cannot escape giving a programmer unfettered access to manipulate memory, so the problem is not in the compiler. There are safe subsets of C that don’t exhibit these problems, but a compiler that only supports such a subset is no longer a C compiler.Thanks, guess that makes sense, kinda.