[Issue 17465] stringof is allowed as identifier
https://issues.dlang.org/show_bug.cgi?id=17465 Jacob Carlborgchanged: What|Removed |Added CC||d...@me.com --- Comment #1 from Jacob Carlborg --- Many of the built-in properties can be used as identifiers, not only stringof. I would prefer if all or most of them would move to a different namespace, like __traits. --
[Issue 17460] Debugger: registers don't work in expression evaluation
https://issues.dlang.org/show_bug.cgi?id=17460 --- Comment #2 from Manu--- Mmm, would be cool. --
[Issue 17465] New: stringof is allowed as identifier
https://issues.dlang.org/show_bug.cgi?id=17465 Issue ID: 17465 Summary: stringof is allowed as identifier Product: D Version: D2 Hardware: All URL: http://dlang.org/ OS: All Status: NEW Severity: minor Priority: P3 Component: dmd Assignee: nob...@puremagic.com Reporter: b2.t...@gmx.com Maybe its usage as identifier should be deprecated ? --- import std.stdio; class Foo { static class stringof { } } void main() { writeln(Foo.stringof); } --- --
[Issue 17461] Bad codegen: compiler emit's call to destructor for uninitialised temporary
https://issues.dlang.org/show_bug.cgi?id=17461 ZombineDevchanged: What|Removed |Added CC||petar.p.ki...@gmail.com --
[Issue 14591] [SPEC] Ambiguity between extern(Pascal) and template value parameters
https://issues.dlang.org/show_bug.cgi?id=14591 ZombineDevchanged: What|Removed |Added CC||petar.p.ki...@gmail.com --
[Issue 17460] Debugger: registers don't work in expression evaluation
https://issues.dlang.org/show_bug.cgi?id=17460 Rainer Schuetzechanged: What|Removed |Added CC||r.sagita...@gmx.de --- Comment #1 from Rainer Schuetze --- > Can the D debugger also evaluate registers in expressions? It currently cannot, but I have also missed that from time to time. Especially when entering the register into the address line of the memory window. --
[Issue 17453] I Have Many Issues
https://issues.dlang.org/show_bug.cgi?id=17453 --- Comment #8 from Rainer Schuetze--- > still cant list the member after "l.?" "this.?". It seems you might be running into something similar to issue 17260. I cannot reproduce locally with your example, but it very much depends on the full source code and especially the imports. Does the status line continue to display "Pending semantic analysis request"? I've also made a few improvements recently. You might want to try the preliminary build from appveyor: https://ci.appveyor.com/project/rainers/visuald/build/job/p04yes499l3omkcr/artifacts --
[Issue 17448] Move semantics cause memory corruption and cryptic bugs
https://issues.dlang.org/show_bug.cgi?id=17448 --- Comment #18 from Walter Bright--- (In reply to Walter Bright from comment #17) > Another case: > > https://github.com/dlang/dmd/pull/6852 Also: https://github.com/dlang/dmd/pull/6849 https://github.com/dlang/dmd/pull/6847 The three of them eliminates the moving in this test case. I know it is not what you're asking for, but it is a worthwhile optimization. --
[Issue 17448] Move semantics cause memory corruption and cryptic bugs
https://issues.dlang.org/show_bug.cgi?id=17448 --- Comment #17 from Walter Bright--- Another case: https://github.com/dlang/dmd/pull/6852 --