Simplification of @trusted

[GrimMaple]

On Wednesday, 16 June 2021 at 16:22:24 UTC, RazvanN wrote:
> On Wednesday, 16 June 2021 at 16:17:28 UTC, GrimMaple wrote:
>> On Wednesday, 16 June 2021 at 15:58:23 UTC, RazvanN wrote:
>>> On Wednesday, 16 June 2021 at 14:57:19 UTC, GrimMaple wrote:
>
>> With my approach, you can still cover as many code @safe as 
>> you want without lying to the end user about the function 
>> safety. IMHO, if you perform @trusted operations in a @safe 
>> function, the function cannot be called @safe .
>
> But this is not true. As Paul Backus pointed out, you can still 
> have
> a @safe function that calls trusted functions. Your argument 
> seems
> to imply that @safe should never interact with @trusted code, 
> which
> to be honest will make it unusable.
>
It's already broken, so let's break it even more? :)