D perfomance

[John Colvin]

On Monday, 27 April 2020 at 14:26:50 UTC, Timon Gehr wrote:
>
> No, it is not analogous, because only @system or @trusted code 
> can get that wrong, not @safe code. @safe code itself is 
> (supposed to be) verified, not trusted.

the existence of any overly @trusting code renders @safe code 
liable to cause memory safety bugs. While the invalid accesses 
won't occur inside @safe code, they can definitely be caused by 
them, even without the buggy @safe code calling any @trusted.

Some day I'll have time to write up all my (many, many pages of) 
notes for this stuff... would have been for dconf, I guess now 
for dconf online?