[Issue 16302] Add opStaticIndex that takes compile-time indices

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16302 Yuxuan Shui changed: What|Removed |Added CC||yshu...@gmail.com --- Comment #6 from Yuxuan S

[Issue 17361] latest windows 10 insider preview and dmd no longer runs.

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17361 --- Comment #5 from steven kladitis --- The latest build and like magic DMD is running again! Version 1703 OS BUILD 16193.1001 A few other programs that stopped are working again also. Thanks, Steven --

[Issue 16302] Add opStaticIndex that takes compile-time indices

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16302 --- Comment #5 from Walter Bright --- (In reply to Steven Schveighoffer from comment #4) > I really would like to see this, and it's pretty straightforward how it > would look, so I will write a DIP to see if there is interest. Great! --

[Issue 16301] CTFE execution of opApply keeps wrong "this" context in foreach's body

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16301 Walter Bright changed: What|Removed |Added Keywords||CTFE --

[Issue 16301] CTFE execution of opApply keeps wrong "this" context in foreach's body

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16301 --- Comment #4 from Walter Bright --- The following simpler code reproduces the problem: struct OpApply { void opApply(void delegate() dlg) { dlg(); } } struct Foo { int i; int abc() { auto o = O

[Issue 16301] CTFE execution of opApply keeps wrong "this" context in foreach's body

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16301 --- Comment #3 from Walter Bright --- (In reply to ag0aep6g from comment #2) > I think you're mistaken. You're right. It is a CTFE problem. --

[Issue 16302] Add opStaticIndex that takes compile-time indices

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16302 --- Comment #4 from Steven Schveighoffer --- I really would like to see this, and it's pretty straightforward how it would look, so I will write a DIP to see if there is interest. --

[Issue 17289] With Xcode 8.3 linker, warnings of "pointer not aligned"

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17289 Zach the Mystic changed: What|Removed |Added CC||reachz...@gmail.com --- Comment #8 from Za

[Issue 16301] CTFE execution of opApply keeps wrong "this" context in foreach's body

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16301 ag0ae...@gmail.com changed: What|Removed |Added CC||ag0ae...@gmail.com --- Comment #2 from a

[Issue 16197] Constructors/postblits and destructors don't match up for array initialisation

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16197 --- Comment #14 from Walter Bright --- (In reply to Eyal from comment #13) > So the bug can be closed as fixed afaic. Thanks! But I still think you'll like the PR I made for this, as it improves performance. --

[Issue 16302] Add opStaticIndex that takes compile-time indices

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16302 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #3 from

[Issue 16301] CTFE execution of opApply keeps wrong "this" context in foreach's body

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16301 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #1 from

[Issue 16197] Constructors/postblits and destructors don't match up for array initialisation

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16197 --- Comment #13 from Eyal --- The dmd output was correct (ignoring irrelevant POSTBLIT -1) - w.r.t number of ctors/postblits & dtors. The ldc output is now correct in version: LDC - the LLVM D compiler (1.1.0git-3139c87): based on DMD v2.071.2 and

[Issue 17156] Local function declaration not inferred to be static

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17156 --- Comment #2 from Eyal --- I see, but this would not be a problem if function was automatically convertible to delegate (std.functional : toDelegate). Is there any reason that you cannot hand over functions when delegates are expected? I'd expect

[Issue 17138] Warn about superfluous "with" statements

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17138 --- Comment #2 from Eyal --- struct Object { auto acquired() { struct Acquired { Object obj; this(Object* obj) { this.obj = obj; obj.acquire(); } ~this() { obj.release(); } } return Acquired(&this); }

[Issue 17394] std.file.mkdirRecurse isn't @safe

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17394 --- Comment #1 from greensunn...@gmail.com --- PR: https://github.com/dlang/phobos/pull/5386 --

[Issue 17395] New: std.file.rmdirRecurse isn't @safe

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17395 Issue ID: 17395 Summary: std.file.rmdirRecurse isn't @safe Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement Priorit

[Issue 17394] New: std.file.mkdirRecurse isn't @safe

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17394 Issue ID: 17394 Summary: std.file.mkdirRecurse isn't @safe Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement Priorit

[Issue 16197] Constructors/postblits and destructors don't match up for array initialisation

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16197 Walter Bright changed: What|Removed |Added Severity|critical|enhancement --- Comment #12 from Walter Brig

[Issue 16197] Constructors/postblits and destructors don't match up for array initialisation

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16197 --- Comment #11 from Walter Bright --- Another effect you are seeing is default construction, which should account for more destructors and postblits than constructor calls. --

[Issue 16197] Constructors/postblits and destructors don't match up for array initialisation

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16197 David Nadlinger changed: What|Removed |Added Severity|enhancement |critical --- Comment #10 from David Nadlin

[Issue 16197] Constructors/postblits and destructors don't match up for array initialisation

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16197 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com Severity|

[Issue 17393] New: AllocatorList leaks memory in "ouroboros mode"

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17393 Issue ID: 17393 Summary: AllocatorList leaks memory in "ouroboros mode" Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: normal

[Issue 17392] New: Add Dub file for the lexer and parser

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17392 Issue ID: 17392 Summary: Add Dub file for the lexer and parser Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement Priority

[Issue 17387] static struct this(ref) not pure

2017-05-12 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17387 --- Comment #2 from Nick Treleaven --- Yes, thanks. What I was confused by was actually when the struct is defined inside the unittest with the static keyword - pure is not inferred. Non-static nested struct inference works, it seemed weird that addi