[Issue 18129] Function parameter 'scope' does not mean without @safe

2018-03-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18129 John Hall changed: What|Removed |Added CC||john.michael.h...@gmail.com --- Comment #1 from

[Issue 18129] Function parameter 'scope' does not mean without @safe

2018-03-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18129 Jonathan M Davis changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 18129] Function parameter 'scope' does not mean without @safe

2018-03-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18129 --- Comment #3 from John Hall --- 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. --

[Issue 18129] Function parameter 'scope' does not mean without @safe

2018-03-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18129 --- Comment #4 from Jonathan M Davis --- 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 parameter

[Issue 18129] Function parameter 'scope' does not mean without @safe

2018-03-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18129 --- Comment #5 from John Hall --- Ah, you're right. It says "Errors for scope violations are only reported in @safe code." --