D perfomance

[Timon Gehr]

On 29.04.20 00:36, ag0aep6g wrote:
> On 28.04.20 15:44, John Colvin wrote:
>> 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.
> 
> I don't see how you arrive at "buggy @safe code" here. You say it 
> yourself: When there is "overly @trusted code", then that's where the 
> bug is.

I guess he is talking about the case where @trusted code calls buggy 
@safe code and relies on it being correct to ensure memory safety. 
(However, this is still the fault of the @trusted code. @safe code 
cannot be blamed for violations of memory safety.)