Retrofitting Temporal Memory Safety on C++

To have so many problems with dangling pointers, Google must be doing something wrong with its C++ coding.

It's amazing to me that they spend so much time trying to circumvent these issues instead of solving the core problems with their development methodology.

And before someone saying 'but C++ code at Google is too large', I'd like to point out that in other industries there is a lot more C++ code but they don't have such issues...e.g. automobiles, where the code in a car might reach the likes of 100 million LOC, mostly in C and C++.