@system blocks and safer @trusted (ST) functions

[Dominikus Dittes Scherkl]

On Sunday, 25 July 2021 at 12:05:10 UTC, Steven Schveighoffer 
wrote:
> The name is the important change. A `@safe` function shouldn't 
> require manual verification. A `@trusted` function does. The 
> `@safe` function with `@trusted` escape gives the impression 
> that the `@safe` parts don't need checking, but they do. It's 
> also difficult to use tools to check which parts need review 
> when focusing on memory safety.

Yes, I agree.
First I was skeptical about this DIP, but that I think is the 
important advantage above @trusted blocks. So I would support 
this DIP.