[Issue 17451] ICE in ddmd/declaration.d(2179)

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17451 --- Comment #6 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/a98029d193806d78d4c3a8ad30adbfa07822f0ae fix Issue 17451 - ICE in ddmd/declaration.d(2179)

[Issue 17352] [REG 2.075a] Internal error: ddmd/backend/elfobj.c 1739 on duplicate definition

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17352 --- Comment #5 from Martin Nowak --- (In reply to Ketmar Dark from comment #4) > i mean, yes, the frontend should check for conflicting overloads even if > they weren't called anywhere. Could be easily checked in overloadInsert et.al.

[Issue 17453] I Have Many Issues

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17453 --- Comment #7 from Soar --- > > 3.can more good support for IntelliSense? such like "this.?" "variable.?" > > You might want to have a look at the language optionss (accessible through > the Visual D menu), especially "show

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17448 Stanislav Blinov changed: What|Removed |Added CC|

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17448 --- Comment #14 from Andrei Alexandrescu --- (In reply to Eyal from comment #13) > (In reply to Andrei Alexandrescu from comment #10) > > > Indeed, the spec should clarify under what circumstances objects can be > > moved. > >

[Issue 17457] Named Return Value Optimization (NRVO) not done with return of constructor call

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17457 --- Comment #1 from Walter Bright --- https://github.com/dlang/dmd/pull/6847 --

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17448 Walter Bright changed: What|Removed |Added See Also|

[Issue 17457] Named Return Value Optimization (NRVO) not done with return of constructor call

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17457 Walter Bright changed: What|Removed |Added See Also|

[Issue 17457] New: Named Return Value Optimization (NRVO) not done with return of constructor call

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17457 Issue ID: 17457 Summary: Named Return Value Optimization (NRVO) not done with return of constructor call Product: D Version: D2 Hardware: All OS: All

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

2017-05-31 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17448 --- Comment #13 from Eyal --- (In reply to Andrei Alexandrescu from comment #10) > Indeed, the spec should clarify under what circumstances objects can be > moved. Could we get compile-time errors when we accidentally do something