Re: DIP1028 - Rationale for accepting as is

[Walter Bright via Digitalmars-d-announce]

On 5/24/2020 2:29 AM, Panke wrote:

I've always understood that the @safe,@trusted,@system machinery provides the following guarantee once all holes are fixed:

If I have a memory corruption in my code than I need to only look at the @trusted and @system parts to find it.

Marking whatevs @safe violates this, marking it @trusted does not.

It's a fair point, but without the source code the distinction is meaningless.