Yes. Good thing about C/C++ (particularly code with statically allocated memory and zero or few virtual calls) is that the resulting code behavior is very predi

Yes. Good thing about C/C++ (particularly code with statically allocated memory and zero or few virtual calls) is that the resulting code behavior is very predictable. You can almost always expect it to be memory bound, and by counting your memory accesses and cache misses guesstimate the performance really well. I guess, that adding memory safety layer may destroy that predictability. If it does, than no - it needs to be optional.