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

[Nick Sabalausky (Abscissa) via Digitalmars-d]

On 02/26/2017 12:17 AM, Ola Fosheim Grostad wrote:
> 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.
>

"Bad things happen" by a different name smells just as foul.