Rationale for accepting DIP 1028 as is

[H. S. Teoh]

On Thu, May 28, 2020 at 03:21:09AM -0600, Jonathan M Davis via Digitalmars-d-announce wrote:
[...]
> With the DIP in its current state, @safe becomes a lie.  The compiler
> no longer guarantees that @safe code is memory safe so long as it
> doesn't call any @trusted code where the programmer incorrectly marked
> it as @trusted. Instead, the compiler blindly treats non-extern(D)
> declarations as @safe and invisibly introduces memory safety bugs into
> @safe code.  Nothing about that is "OK."
[...]

I see it already.  The next time someone wants to make a codebase @safe
but the compiler complains about some violation, just add `extern(C)` to
the function and move on.


T

-- 
Claiming that your operating system is the best in the world because more people use it is like saying McDonalds makes the best food in the world. -- Carl B. Constantine