April 06, 2018 [Issue 17906] Deprecated Language features should be allowed without a deprecation in a deprecated scope | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=17906 Issue 17906 depends on issue 18647, which changed state. Issue 18647 Summary: Use of delete should be allowed without a deprecation in a deprecated scope https://issues.dlang.org/show_bug.cgi?id=18647 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- |
November 23, 2022 [Issue 17906] Deprecated Language features should be allowed without a deprecation in a deprecated scope | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=17906 RazvanN <razvan.nitu1305@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |razvan.nitu1305@gmail.com Resolution|--- |WORKSFORME --- Comment #7 from RazvanN <razvan.nitu1305@gmail.com> --- I cannot reproduce this. I have used this example: deprecated void main () @safe { toString(null); } deprecated void toString (void delegate (char[]) @safe sink) @safe { char[20] buffer = void; sink(unsignedToTempString(42, buffer)); } With the functions not being deprecated, you get a deprecation about assigning buffer to the anonymous parameter of synk, but with the functions being deprecated the message is silenced. Closing as WORKSFORME. -- |
Copyright © 1999-2021 by the D Language Foundation