Re: DIP1028 - Rationale for accepting as is

[Walter Bright via Digitalmars-d-announce]

I infer your position is the idea that putting @trusted on the declarations 
isn't greenwashing, while @safe is.

I can't see a practical difference between:
@safe extern (C) void whatevs(parameters);
@trusted extern (C) void whatevs(parameters);

Both require that whatevs() provide a safe interface. The difference between 
them is in the implementation of those functions, not the interface. Since the D 
compiler cannot see those implementations, they are immaterial to the compiler 
and user.