[Issue 18493] [betterC] Can't use aggregated type with postblit

https://issues.dlang.org/show_bug.cgi?id=18493 --- Comment #3 from Radu Racariu --- Declaring `C` as --- struct C { S s1; } --- makes the test case compile. --

[Issue 18419] make all Phobos unittests version(StdUnittest)

https://issues.dlang.org/show_bug.cgi?id=18419 Nathan S. changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18768] object.getArrayHash with custom toHash shouldn't just sum hashes of array elements

https://issues.dlang.org/show_bug.cgi?id=18768 --- Comment #1 from Nathan S. --- Pull request: https://github.com/dlang/druntime/pull/2166 --

[Issue 18767] __xtoHash memberwise hashing shouldn't just sum the member hashes

https://issues.dlang.org/show_bug.cgi?id=18767 --- Comment #1 from Nathan S. --- Pull request: https://github.com/dlang/druntime/pull/2166 --

[Issue 18768] New: object.getArrayHash with custom toHash shouldn't just sum hashes of array elements

https://issues.dlang.org/show_bug.cgi?id=18768 Issue ID: 18768 Summary: object.getArrayHash with custom toHash shouldn't just sum hashes of array elements Product: D Version: D2 Hardware: All OS: All

[Issue 18767] New: __xtoHash memberwise hashing shouldn't just sum the member hashes

https://issues.dlang.org/show_bug.cgi?id=18767 Issue ID: 18767 Summary: __xtoHash memberwise hashing shouldn't just sum the member hashes Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 18766] std.typecons.Tuple.toHash could be improved

https://issues.dlang.org/show_bug.cgi?id=18766 Nathan S. changed: What|Removed |Added Severity|minor |enhancement --

[Issue 18766] std.typecons.Tuple.toHash could be improved

https://issues.dlang.org/show_bug.cgi?id=18766 --- Comment #1 from Nathan S. --- Pull request: https://github.com/dlang/phobos/pull/6457 --

[Issue 18766] New: std.typecons.Tuple.toHash could be improved

https://issues.dlang.org/show_bug.cgi?id=18766 Issue ID: 18766 Summary: std.typecons.Tuple.toHash could be improved Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: minor

[Issue 18757] static invariant{} should either work or not be valid syntax

https://issues.dlang.org/show_bug.cgi?id=18757 Andrei Alexandrescu changed: What|Removed |Added CC||and...@erdani.com

[Issue 18757] static invariant{} should either work or not be valid syntax

https://issues.dlang.org/show_bug.cgi?id=18757 Walter Bright changed: What|Removed |Added CC|

[Issue 18757] static invariant{} should either work or not be valid syntax

https://issues.dlang.org/show_bug.cgi?id=18757 --- Comment #6 from FeepingCreature --- In my opinion, static this sets the precedent that static + class-level feature = module-level feature. --

[Issue 18757] static invariant{} should either work or not be valid syntax

https://issues.dlang.org/show_bug.cgi?id=18757 Jonathan M Davis changed: What|Removed |Added CC|

[Issue 18719] Doubly-called constructor against member when using forwarding constructors

https://issues.dlang.org/show_bug.cgi?id=18719 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18719] Doubly-called constructor against member when using forwarding constructors

https://issues.dlang.org/show_bug.cgi?id=18719 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/cbb49cb2591bd5aa3e5f9e0b8a4350cb04ec1206 Fix Issue 18719 - Doubly-called constructor against member

[Issue 18762] DMD should use a unique path/filename for __stdin.o

for __stdin.o https://github.com/dlang/dmd/commit/bfb89f5099f4607d2b56a0508b3bbc6cec800de3 Merge pull request #8174 from CyberShadow/pull-20180416-133742 Fix Issue 18762 - DMD should use a unique path/filename for __stdin.o merged-on-behalf-of: Andrei Alexandrescu <andra...@users.noreply.github.com> --

[Issue 18762] DMD should use a unique path/filename for __stdin.o

https://issues.dlang.org/show_bug.cgi?id=18762 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18757] static invariant{} should either work or not be valid syntax

https://issues.dlang.org/show_bug.cgi?id=18757 --- Comment #4 from RazvanN --- (In reply to uplink.coder from comment #3) > Well invariants cannot apply to static methods since they are only concerned > about the object's state. > which by definition cannot be directly

[Issue 18757] static invariant{} should either work or not be valid syntax

https://issues.dlang.org/show_bug.cgi?id=18757 uplink.co...@googlemail.com changed: What|Removed |Added CC||uplink.co...@googlemail.com

[Issue 18757] static invariant{} should either work or not be valid syntax

https://issues.dlang.org/show_bug.cgi?id=18757 --- Comment #2 from FeepingCreature --- In case 1, I maintain that this is a bug - the compiler should not smile-and-nod while silently ignoring syntax that hints at a semantic that does not apply. --

[Issue 18762] DMD should use a unique path/filename for __stdin.o

https://issues.dlang.org/show_bug.cgi?id=18762 Vladimir Panteleev changed: What|Removed |Added Keywords||pull

[Issue 18757] static invariant{} should either work or not be valid syntax

https://issues.dlang.org/show_bug.cgi?id=18757 RazvanN changed: What|Removed |Added CC|

[Issue 18736] constructor calls allowed after case labels

https://issues.dlang.org/show_bug.cgi?id=18736 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/15f525620895727147cf12e33596ae1a2d3ffa45 fix Issue 18736 - constructor calls allowed after case labels

[Issue 18472] [Reg 2.078] betterC: cannot use format at compile time.

https://issues.dlang.org/show_bug.cgi?id=18472 --- Comment #10 from Mike Franklin --- PR 8173 seems to take care of the case... module betterc; enum b = typeid(size_t) is typeid(uint) ... but still fails for ... import std.format; import std.stdio; void main() { enum

[Issue 18756] Escaping address of temporary struct field

https://issues.dlang.org/show_bug.cgi?id=18756 --- Comment #4 from Jonathan M Davis --- (In reply to anonymous4 from comment #3) > (In reply to Jonathan M Davis from comment #2) > > because it's always a bug. > It's correct when the result is passed to a function

[Issue 18472] [Reg 2.078] betterC: cannot use format at compile time.

https://issues.dlang.org/show_bug.cgi?id=18472 Mike Franklin changed: What|Removed |Added Keywords||pull --- Comment #9

[Issue 18756] Escaping address of temporary struct field

https://issues.dlang.org/show_bug.cgi?id=18756 anonymous4 changed: What|Removed |Added Hardware|x86 |All

[Issue 18472] [Reg 2.078] betterC: cannot use format at compile time.

https://issues.dlang.org/show_bug.cgi?id=18472 --- Comment #8 from Mike Franklin --- (In reply to Rainer Schuetze from comment #7) > I think the main issue is that the compiler does not distinguish between > information needed at compile time and what's necessary inside the