DIP1028 - Rationale for accepting as is

[Paolo Invernizzi]

On Friday, 22 May 2020 at 17:54:26 UTC, Atila Neves wrote:
> On Friday, 22 May 2020 at 17:41:38 UTC, Steven Schveighoffer

>> And so, you are free to pepper your @safe code with dangling 
>> pointers. Sure, you can claim that the C++ library didn't 
>> "corrupt your code", which is the case for ALL libraries if 
>> you use them properly. You did it, you created a dangling 
>> pointer, not the library.
>
> Right. And the point I was trying to make wasn't "look at what 
> I did, it's cool". No, what I did was dumb. So dumb it took you 
> no time at all to point out one of my mistakes. My point is 
> that the result of making declarations implicity @system 
> instead of @safe would make people just slap @safe on them 
> without really thinking about it to get their code to compile. 
> Like I did.

So force people to slap @trusted instead, via compiler complains, 
not @safe, and reviewers will catch the laziness: why this is 
worst that what you picture?