Both safe and wrong?

[Olivier FAURE]

On Monday, 4 February 2019 at 20:36:23 UTC, Walter Bright wrote:
> I listed it as a "normal" bug rather than "enhancement". I 
> believe that answers your question.

Are you confirming that the documentation in 
https://dlang.org/spec/memory-safe-d.html will be updated to 
refer to "safe code" instead of just safe functions?

Anyway, thinking about it, I think fixing this elegantly might 
require coming up with new semantics. How do you make sure that 
no @system code is called in your project without manually 
checking every single variable declaration in your dependencies? 
Checking that functions are @safe is easy because @system is 
infectious, so you only have to check for @trusted code, but 
there's no way to make global variable safety infectious, is 
there?