[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 Dlang Bot changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #11 from Dlang Bot ---

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 ki...@gmx.net changed: What|Removed |Added CC||ki...@gmx.net --- Comment #10 from

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 --- Comment #9 from uplink.co...@googlemail.com --- (In reply to Andrei Alexandrescu from comment #6) > (In reply to ag0aep6g from comment #5) > > You have to initialize the int[3], as you did with the int. I suppose the > > compiler assumes that

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 Mathias Lang changed: What|Removed |Added CC|

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 --- Comment #8 from ag0ae...@gmail.com --- (In reply to Andrei Alexandrescu from comment #6) > Now, Lucia (@somzzz) has gotten to the point where it all passes druntime > and phobos unittests, but breaks in exactly one point in the compiler. It > can

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

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

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 --- Comment #7 from Andrei Alexandrescu --- I meant: bool __equals(L, R)(L[] lhs, R[] rhs); bool __equals(L, R, size_t n1)(auto ref L[n1] lhs, R[] rhs); bool __equals(L, R, size_t n2)(auto ref L[] lhs, auto ref R[n2] rhs); bool

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 --- Comment #6 from Andrei Alexandrescu --- (In reply to ag0aep6g from comment #5) > You have to initialize the int[3], as you did with the int. I suppose the > compiler assumes that you're going to do run-time initialization via

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 ag0ae...@gmail.com changed: What|Removed |Added CC||ag0ae...@gmail.com --- Comment #5 from

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 --- Comment #4 from uplink.co...@googlemail.com --- As far as I can see there is no special treatment. CTFE does only work on literals results of ctfe evaluations are always literals. --

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

https://issues.dlang.org/show_bug.cgi?id=17351 Andrei Alexandrescu changed: What|Removed |Added Status|RESOLVED|REOPENED

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

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

[Issue 17351] Static const array can't be evaluated at compile time when passed as ref argument

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