This brings up a question. I think we can all agree that detecting an overrun shows a fault in the system. But does it create an error?

Could this could be changed to where the overflow does not cause an abort; rather the next read of that location, without a corresponding legal write causes the abort. A buffer overrun does not mean the answer is wrong, but the use of memory that was overrun will.

In that case, production or not, you would want an abort. The answer is wrong!

(Perhaps this makes no sense. If so, sorry, the idea just came to me after reading the article.)