https://issues.dlang.org/show_bug.cgi?id=13864

Vlad Levenfeld <vlevenfeld@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vlevenfeld@gmail.com

--

https://issues.dlang.org/show_bug.cgi?id=13864

hsteoh@quickfur.ath.cx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsteoh@quickfur.ath.cx

--- Comment #1 from hsteoh@quickfur.ath.cx ---
Seems to work in git HEAD, tested on Linux/64. Maybe this has already been fixed?

--

https://issues.dlang.org/show_bug.cgi?id=13864

--- Comment #2 from Vlad Levenfeld <vlevenfeld@gmail.com> ---
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[0];
        writeln (x[0.tuple.expand]); // ok

and this:
        writeln  (x[0]);
        auto z = x[0.tuple.expand]; // ok

not sure whats going on, I just recompiled dmd from the latest

--

https://issues.dlang.org/show_bug.cgi?id=13864

--- Comment #3 from Vlad Levenfeld <vlevenfeld@gmail.com> ---
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 #4 from Vlad Levenfeld <vlevenfeld@gmail.com> ---
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 commented out
        f (x[0.tuple.expand]);
    }

--

https://issues.dlang.org/show_bug.cgi?id=13864

--- Comment #5 from Vlad Levenfeld <vlevenfeld@gmail.com> ---
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 soon as that line is reached.

--

https://issues.dlang.org/show_bug.cgi?id=13864

Kenji Hara <k.hara.pg@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code
           Hardware|x86_64                      |All
            Summary|tuple expand causes range   |[REG2.066] tuple expand
                   |violation                   |causes range violation
                 OS|Linux                       |All
           Severity|major                       |regression

--- Comment #6 from Kenji Hara <k.hara.pg@gmail.com> ---
https://github.com/D-Programming-Language/dmd/pull/4216

--

https://issues.dlang.org/show_bug.cgi?id=13864

Kenji Hara <k.hara.pg@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |pull

--

https://issues.dlang.org/show_bug.cgi?id=13864

--- Comment #7 from github-bugzilla@puremagic.com ---
Commits pushed to master at https://github.com/D-Programming-Language/dmd

https://github.com/D-Programming-Language/dmd/commit/872a1b649c3a13f3a6b1bcfdec8e6961671411eb fix Issue 13864 - tuple expand causes range violation

https://github.com/D-Programming-Language/dmd/commit/626d64259c0d6d8ebbe6bb54da816558d6137306 Merge pull request #4216 from 9rnsr/fix13864

[REG2.066] Issue 13864 - tuple expand causes range violation

--

https://issues.dlang.org/show_bug.cgi?id=13864

github-bugzilla@puremagic.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--