https://issues.dlang.org/show_bug.cgi?id=18129

John Hall <john.michael.hall@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |john.michael.hall@gmail.com

--- Comment #1 from John Hall <john.michael.hall@gmail.com> ---
This may be related to issue 6931 [1].

Regardless, I tried simpler and some more complex variations on what you did and also got the same result.


[1] https://issues.dlang.org/show_bug.cgi?id=6931

--

https://issues.dlang.org/show_bug.cgi?id=18129

Jonathan M Davis <issues.dlang@jmdavisProg.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |issues.dlang@jmdavisProg.co
                   |                            |m
         Resolution|---                         |DUPLICATE

--- Comment #2 from Jonathan M Davis <issues.dlang@jmdavisProg.com> ---
Without -dip1000, scope is ignored on parameters for everything other than delegates. DIP 1000 is expanding on scope to fully implement it for pointers and dynamic arrays and whatnot, but without DIP 1000, it does almost nothing.

*** This issue has been marked as a duplicate of issue 6931 ***

--

https://issues.dlang.org/show_bug.cgi?id=18129

--- Comment #3 from John Hall <john.michael.hall@gmail.com> ---
Jonathan, I was a little hesitant to say I was sure it was a duplicate of that one because I tried running it on run.dlang.org with the -dip1000 flag and it was still not giving a warning.

--

https://issues.dlang.org/show_bug.cgi?id=18129

--- Comment #4 from Jonathan M Davis <issues.dlang@jmdavisProg.com> ---
As I understand it, -dip1000 has no effect on code that isn't @safe. So, you're not going to have the compiler yelling at you over it if you're not using @safe. Either way, without -dip1000, scope on parameters only affects delegates and thus has no effect on the code posted here.

--

https://issues.dlang.org/show_bug.cgi?id=18129

--- Comment #5 from John Hall <john.michael.hall@gmail.com> ---
Ah, you're right. It says "Errors for scope violations are only reported in @safe code."

--