Thread overview
[Issue 4695] New: std.range.zip is broken
Aug 20, 2010
Max Klyga
Aug 28, 2010
David Simcha
Apr 21, 2012
SomeDude
August 20, 2010
http://d.puremagic.com/issues/show_bug.cgi?id=4695

           Summary: std.range.zip is broken
           Product: D
           Version: D2
          Platform: Other
        OS/Version: Mac OS X
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Phobos
        AssignedTo: nobody@puremagic.com
        ReportedBy: necroment@gmail.com


--- Comment #0 from Max Klyga <necroment@gmail.com> 2010-08-20 15:12:41 PDT ---
import std.range;

void main() {
    auto a = [ 1, 2, 3 ];
    immutable b = [ 1, 2, 3 ];
    zip(a, b);
}

outputs:
src/phobos/std/range.d(1732): Error: can only initialize const member
_field_field_1 inside constructor

import std.range;

void main() {
    auto a = [ 1, 2, 3 ];
    auto b = [ 'a', 'b', 'c' ];
    zip(a, b);
}

outputs:
src/phobos/std/range.d(1773): Error: front(this.ranges._field_field_1) is not
an lvalue

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
August 28, 2010
http://d.puremagic.com/issues/show_bug.cgi?id=4695


David Simcha <dsimcha@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dsimcha@yahoo.com


--- Comment #1 from David Simcha <dsimcha@yahoo.com> 2010-08-28 13:17:34 PDT ---
Thanks for the report.  I just wanted to note that this is more of a design issue than an implementation bug.  The lack of tail const makes making higher order ranges work properly for const/immutable ranges impossible except in some special cases.  (const/immutable arrays are one of these special cases.)  This flaw may eventually get fixed, or we may eventually special case everything to work with at least const/immutable arrays, but there are deeper issues that need to be resolved before this gets fixed.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
January 09, 2011
http://d.puremagic.com/issues/show_bug.cgi?id=4695


Andrei Alexandrescu <andrei@metalanguage.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |andrei@metalanguage.com
         AssignedTo|nobody@puremagic.com        |andrei@metalanguage.com


-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
April 21, 2012
http://d.puremagic.com/issues/show_bug.cgi?id=4695


SomeDude <lovelydear@mailmetrash.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lovelydear@mailmetrash.com


--- Comment #2 from SomeDude <lovelydear@mailmetrash.com> 2012-04-21 15:27:13 PDT ---
Works on 2.059

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
April 22, 2012
http://d.puremagic.com/issues/show_bug.cgi?id=4695


bearophile_hugs@eml.cc changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
                 CC|                            |bearophile_hugs@eml.cc
         Resolution|                            |FIXED


--- Comment #3 from bearophile_hugs@eml.cc 2012-04-22 03:45:36 PDT ---
While the general problem is not solved, this specific problem with arrays is solved.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------