[Issue 17966] chunkBy cannot accept an input range (from multiwayMerge)

https://issues.dlang.org/show_bug.cgi?id=17966 Jon Degenhardt changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Issue 16169] nWayUnion assertion failure

https://issues.dlang.org/show_bug.cgi?id=16169 Jon Degenhardt changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 19532] chunkBy assert error involving non-forward input ranges.

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

[Issue 19532] chunkBy assert error involving non-forward input ranges.

https://issues.dlang.org/show_bug.cgi?id=19532 --- Comment #7 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/b17984059e3dd0a0a4afc696b7f5696bf3c54826 Fix Issue 19532 - chunkBy errors involving non-forward

[Issue 19441] alias this causes partial assignment

https://issues.dlang.org/show_bug.cgi?id=19441 --- Comment #7 from Stefan Koch --- Eyal, I guess you could make it such that you error out if alias-this ever conflicts with anything. Which would be a solution that properly fixes unwanted overload-stealing. However that'll break a lot of code,

[Issue 19441] alias this causes partial assignment

https://issues.dlang.org/show_bug.cgi?id=19441 --- Comment #6 from Eyal --- Stefan - under what circumstances does prioritizing "alias this" ever help? Anyway, a compiler error - not changed semantics - as proposed here, should be fine (with the ordinary caveat of __traits(compiles ...)).

[Issue 19634] Usual Arithmetic Conversions doesn't define what happens on failure

https://issues.dlang.org/show_bug.cgi?id=19634 Neia Neutuladh changed: What|Removed |Added Keywords||spec --- Comment #1 from Neia Neutuladh

[Issue 19634] New: Usual Arithmetic Conversions doesn't define what happens on failure

https://issues.dlang.org/show_bug.cgi?id=19634 Issue ID: 19634 Summary: Usual Arithmetic Conversions doesn't define what happens on failure Product: D Version: D2 Hardware: x86_64 OS: Linux

[Issue 19633] New: Identity expression produces wrong result with interface inheritance

https://issues.dlang.org/show_bug.cgi?id=19633 Issue ID: 19633 Summary: Identity expression produces wrong result with interface inheritance Product: D Version: D2 Hardware: x86_64 OS: Linux

[Issue 19632] [SIMD] Error: invalid foreach aggregate

https://issues.dlang.org/show_bug.cgi?id=19632 Stefan Koch changed: What|Removed |Added CC||uplink.co...@gmail.com --- Comment #1 from

[Issue 19441] alias this causes partial assignment

https://issues.dlang.org/show_bug.cgi?id=19441 Stefan Koch changed: What|Removed |Added CC||uplink.co...@gmail.com --- Comment #5 from

[Issue 19632] [SIMD] Error: invalid foreach aggregate

https://issues.dlang.org/show_bug.cgi?id=19632 Iain Buclaw changed: What|Removed |Added CC||ibuc...@gdcproject.org

[Issue 19632] New: [CTFE][SIMD] Error: invalid foreach aggregate

https://issues.dlang.org/show_bug.cgi?id=19632 Issue ID: 19632 Summary: [CTFE][SIMD] Error: invalid foreach aggregate Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: major

[Issue 16657] alias this interacts with generated opCmp and opEquals

https://issues.dlang.org/show_bug.cgi?id=16657 --- Comment #10 from Eyal --- I think a new "transition" compiler flag [1] can be added to warn about the changes in behavior here. It is possible to make these warnings the default for a few versions (with a flag to suppress them), but I think

[Issue 16657] alias this interacts with generated opCmp and opEquals

https://issues.dlang.org/show_bug.cgi?id=16657 --- Comment #9 from Andrei Alexandrescu --- Question for everyone: is this worth a deprecation cycle, and if so how would it behave? It's kinda awkward. --

[Issue 19441] alias this causes partial assignment

https://issues.dlang.org/show_bug.cgi?id=19441 --- Comment #4 from Andrei Alexandrescu --- Great you guys. I think it's best to qualify this as an wrong-code bug so we don't go through a deprecation cycle. OK? --

[Issue 19441] alias this causes partial assignment

https://issues.dlang.org/show_bug.cgi?id=19441 --- Comment #3 from Eyal --- Agreed. Assignment should assign the whole thing. --

[Issue 19441] alias this causes partial assignment

https://issues.dlang.org/show_bug.cgi?id=19441 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #2

[Issue 19631] Segfault on simple nested templated struct

https://issues.dlang.org/show_bug.cgi?id=19631 --- Comment #2 from Basile-z --- Problem happens when the initializer type is being determined. In case of this issue is blocking some work there are two possible workarounds in addition to the "non nesting" solution. 1. Field!(w, h) a = *new

[Issue 19441] alias this causes partial assignment

https://issues.dlang.org/show_bug.cgi?id=19441 Andrei Alexandrescu changed: What|Removed |Added CC||and...@erdani.com --- Comment #1 from

[Issue 19631] Segfault on simple nested templated struct using DMD64 D Compiler v2.084.0

https://issues.dlang.org/show_bug.cgi?id=19631 Basile-z changed: What|Removed |Added CC||b2.t...@gmx.com Severity|major

[Issue 19631] Segfault on simple nested templated struct

https://issues.dlang.org/show_bug.cgi?id=19631 Basile-z changed: What|Removed |Added Summary|Segfault on simple nested |Segfault on simple nested

[Issue 19631] Segfault on simple nested templated struct using DMD64 D Compiler v2.084.0

https://issues.dlang.org/show_bug.cgi?id=19631 Arne Marschall changed: What|Removed |Added CC||bestellung@marschall-inform

[Issue 19631] New: Segfault on simple nested templated struct using DMD64 D Compiler v2.084.0

https://issues.dlang.org/show_bug.cgi?id=19631 Issue ID: 19631 Summary: Segfault on simple nested templated struct using DMD64 D Compiler v2.084.0 Product: D Version: D2 Hardware: x86_64 OS: Linux