Both safe and wrong?
Walter Bright
newshound2 at digitalmars.com
Thu Feb 7 01:04:44 UTC 2019
On 2/6/2019 2:02 AM, Olivier FAURE wrote:
> 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?
I'm not seeing a problem with it.
More information about the Digitalmars-d
mailing list