DIP1028 - Rationale for accepting as is

[Paolo Invernizzi]

On Friday, 22 May 2020 at 17:07:37 UTC, Atila Neves wrote:

> And so I was convinced that everything being @safe is actually 
> ok, especially because in real life, most C/C++ APIs aren't 
> going to secretly corrupt your code.

Uh? There's plenty of C/C++ code out there with api that when 
"used in the wrong way" will corrupt memory.

That's the _essence_ of @trusted code, the _programmer_ need to 
_correctly_ handle the usage, because the compiler can't do that 
job alone.