D perfomance
ag0aep6g
anonymous at example.com
Tue Apr 28 22:36:21 UTC 2020
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.
More information about the Digitalmars-d
mailing list