On Thursday, 29 December 2016 at 18:21:30 UTC, Stefan Koch wrote:
Hi Guys,
I just figured out why array constants did not work as function
arguments.
It's because the array-constant undergoes a cast when used as
slice, while an array literal can be taken as is.
The currently newCTFE does not really provide the capabilities
to handle casts.
This is another issue that has to be addressed before
function-calls come into play.
Within the engine dynamic and static arrays are represented in
the same structure.
Therefore we don't need to take action on such a cast as long
as the element types are the same.
While simply ignoring the cast-expression is correct in the
case, I need to systemize the handling of casts better.
This is now partially fixed.
Also all the latest work was merged in the feature branch.
The current timeline is still the same, I suspect that newCTFE
will be usable in February.