DIP1028 - Rationale for accepting as is

[Arafel]

On 24/5/20 0:02, ag0aep6g wrote:
> 
> ... and @system static constructors and `--boundscheck=off` and 
> initializers of globals

Other than `--boundscheck=off`, that is presumably actively chosen by 
the user (as is @trust), would the others be allowed without `@trusted` 
in otherwise 100% @safe code?

I would find concerning that any @system code is allowed, but I guess 
initializers of globals should be ok as long as they are @safe themselves?