If you needed any more evidence that memory safety is the future...

[Ola Fosheim Grostad via Digitalmars-d]

On Saturday, 25 February 2017 at 22:37:15 UTC, Chris Wright wrote:
> The undefined behavior is what happens after the would-be 
> assertion failure occurs. The compiler is free to emit code as 
> if the assertion passed, or if there is no way for the 
> assertion to pass, it is free to do anything it wants.

No. That would be implementation defined behaviour. Undefined 
behaviour means the whole program is illegal, i.e. not covered by 
the language at all.