[Issue 17759] struct that attempts to implicitly cast away const causes segfault
https://issues.dlang.org/show_bug.cgi?id=17759 Basile-z changed: What|Removed |Added CC|b2.t...@gmx.com | --
[Issue 17759] struct that attempts to implicitly cast away const causes segfault
https://issues.dlang.org/show_bug.cgi?id=17759 Basile-z changed: What|Removed |Added Status|NEW |RESOLVED CC||b2.t...@gmx.com Resolution|--- |WORKSFORME --- Comment #4 from Basile-z --- fixed since 2.086 --
[Issue 17759] struct that attempts to implicitly cast away const causes segfault
https://issues.dlang.org/show_bug.cgi?id=17759 --- Comment #3 from Steven Schveighoffer --- Hm... so alias this resolution needs some kind of memoization to prevent infinite expansion. Interesting. --
[Issue 17759] struct that attempts to implicitly cast away const causes segfault
https://issues.dlang.org/show_bug.cgi?id=17759 bitter.ta...@gmx.com changed: What|Removed |Added CC||bitter.ta...@gmx.com --- Comment #2 from bitter.ta...@gmx.com --- This happens because the built-in `opEquals' that's synthesized by the compiler contains a condition such as `(p == q)` that's recursively expanded into `(p.foo == q) and `(p.foo.foo == q)`. The problem lies in `resolvePropertiesX' that keeps assembling this crazy chain where the `p' is substituted every step. --
[Issue 17759] struct that attempts to implicitly cast away const causes segfault
https://issues.dlang.org/show_bug.cgi?id=17759 --- Comment #1 from Steven Schveighoffer --- should say, attempts to legally *implicitly* cast away const. --
