[Issue 4305] Take, Chain on top of ranges w/o moveFront()

2010-06-24 Thread d-bugmail 
http://d.puremagic.com/issues/show_bug.cgi?id=4305


David Simcha  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED


--- Comment #2 from David Simcha  2010-06-24 20:07:48 PDT ---
Fixed in SVN.

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

[Issue 4305] Take, Chain on top of ranges w/o moveFront()

2010-06-13 Thread d-bugmail 
http://d.puremagic.com/issues/show_bug.cgi?id=4305


Andrei Alexandrescu  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED


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

[Issue 4305] Take, Chain on top of ranges w/o moveFront()

2010-06-13 Thread d-bugmail 
http://d.puremagic.com/issues/show_bug.cgi?id=4305


Andrei Alexandrescu  changed:

   What|Removed |Added

 CC||and...@metalanguage.com
 AssignedTo|nob...@puremagic.com|and...@metalanguage.com


--- Comment #1 from Andrei Alexandrescu  2010-06-13 
20:54:52 PDT ---
The intent is to allow manipulation of ranges that contain types arbitrarily
expensive to copy. The current design requires either front() to yield a ref,
or the range to define moveFront().

I think a better design is to define the module-level std.range.moveFront() to
issue a simple copy when the type being copied does not define this(this). I'll
do so soon. Thanks!

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