[Issue 19413] Segfault assigning hashmap from slice in CTFE

https://issues.dlang.org/show_bug.cgi?id=19413 --- Comment #5 from Stefan Koch --- Some more information: What happens is actually a stack-overflow in optimize.d:1209 I guess my guess is that error-nodes do compare false to all other nodes since an error node does make it through. the

[Issue 19413] Segfault assigning hashmap from slice in CTFE

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

[Issue 19413] Segfault assigning hashmap from slice in CTFE

https://issues.dlang.org/show_bug.cgi?id=19413 dl...@ryanjframe.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID

[Issue 19413] Segfault assigning hashmap from slice in CTFE

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

[Issue 19413] Segfault assigning hashmap from slice in CTFE

https://issues.dlang.org/show_bug.cgi?id=19413 RazvanN changed: What|Removed |Added CC||razvan.nitu1...@gmail.com --- Comment #2 from

[Issue 19413] Segfault assigning hashmap from slice in CTFE

https://issues.dlang.org/show_bug.cgi?id=19413 --- Comment #1 from dl...@ryanjframe.com --- run.dlang.io runs this successfully from 2.061 to 2.080.1; it segfaults from 2.081.1 to current. --