> "No way to prevent this", Says Only Language Where This Regularly Happens

   clang -fbounds-safety ...

Obviously the way to prevent this is by bounds checking, which is literally in the `770594e` patch. It's just a bug and they happen routinely in all languages. Since this is doing pointer arithmetic, it could just as easily happen in unsafe Rust, for example.

Surely nobody could create a better language in 50 years. Surely we can't fix these issues.

And you see a lot of other languages being used to create operating systems with complicated multiprocessor and locking semantics?