The fact that X doesn't solve all security problems doesn't mean that X doesn't eliminate a whole class of problems. Memory safety problems are still a sizable

The fact that X doesn't solve all security problems doesn't mean that X doesn't eliminate a whole class of problems. Memory safety problems are still a sizable proportion of the CVEs associated with C and C++ programs. > The major compilers already have ways to test for undefined behavior such as -fsanitize=undefined. Projects need to use these flags and test more. This is NOT a solution -- you cannot test every case. In fact, not even close: The possible state space to for signed addition of two 64-bit ints is 2^128. That is infeasible. A compiler for a 'safe' language CAN prove the absence of certain behaviors (UB being one of them).