https://issues.dlang.org/show_bug.cgi?id=13864
--- Comment #5 from Vlad Levenfeld ---
It only seems to happen with T[] types, struct with opIndex to catch and print
args confirms that the tuple expand call just resolves to a 0 int. Np luck
catching it with gdb so far, the violation goes off as so
https://issues.dlang.org/show_bug.cgi?id=13864
--- Comment #4 from Vlad Levenfeld ---
its not writeln, this works as well:
auto f (T...)(T)
{
}
void main (string[] args)
{
int[] x = [2,3,4];
f (x[0]);
auto a = x[0.tuple.expand]; // range violation if
https://issues.dlang.org/show_bug.cgi?id=13864
--- Comment #3 from Vlad Levenfeld ---
this works as well:
writeln (x[0]);
auto y = x[0.tuple.expand];
writeln (x[0.tuple.expand]); // ok again??
--
https://issues.dlang.org/show_bug.cgi?id=13864
--- Comment #2 from Vlad Levenfeld ---
I'm using git HEAD, I still get the range violation. Not only that but this:
auto y = x[0];
auto z = x[0.tuple.expand]; // ok
runs fine. (got rid of writeln)
but also this:
auto y = x
https://issues.dlang.org/show_bug.cgi?id=13864
hst...@quickfur.ath.cx changed:
What|Removed |Added
CC||hst...@quickfur.ath.cx
--- Comment #
https://issues.dlang.org/show_bug.cgi?id=13864
Vlad Levenfeld changed:
What|Removed |Added
CC||vlevenf...@gmail.com
--
