The cool thing about this approach is that it can be designed and implemented without any input from the C++ committee.
The way to think about “memory-safe systems languages” is that they provide *static* memory safety, which provide optimal performance.
But if the language chooses not to statically mitigate defects, then yeah sure, as practitioners we can just choose to employ security measures to guard against them at runtime.