[Issue 13041] std.range.transposed consumes sub-ranges

2017-11-02 Thread d-bugmail--- via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13041

--- Comment #4 from Steven Schveighoffer  ---
It certainly is possible. Note there is current work to update Transposed to
use transverse to allow indexing https://github.com/dlang/phobos/pull/5805.

I think we can go further building upon transverse, and its related option on
how to treat the data.

But it would be a strange relationship between transposed and its subranges. If
the subranges were indexable, then Transposed can be a forward range, otherwise
it can't. Seems unintuitive, and not sure it's worth all the effort.

In other cases as well (if, for instance, the RangeOfRanges stores everything
by value), then save could also be implemented. We may have a hard time
detecting this because the relationship between Transposed and whether it's
valid to make a copy is confusing and not well-established.

--

[Issue 13041] std.range.transposed consumes sub-ranges

2017-11-01 Thread d-bugmail--- via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13041

--- Comment #3 from hst...@quickfur.ath.cx ---
I wonder if there's any possibility of implementing .save for a random-access
range, if the subranges are also random-access.

In this case, we wouldn't need to consume the subranges at all, but can simply
store a set of current indices to implement .transposed.

--

[Issue 13041] std.range.transposed consumes sub-ranges

2017-11-01 Thread d-bugmail--- via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13041

Steven Schveighoffer  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||schvei...@yahoo.com
 Resolution|--- |WONTFIX

--- Comment #2 from Steven Schveighoffer  ---
Given how issue 17952 was resolved (we deprecated transposed being a forward
range, as it would require dup'ing per save), I think we can close this as
WONTFIX.

Once Transposed.save is removed, we can update the docs to reflect that
transposed may consume sub-ranges. I think this is just in the nature of
transposed and how forward ranges are stored.

--

[Issue 13041] std.range.transposed consumes sub-ranges

2017-10-30 Thread d-bugmail--- via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13041

Steven Schveighoffer  changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=17952

--

[Issue 13041] std.range.transposed consumes sub-ranges

2017-07-05 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13041

Vladimir Panteleev  changed:

   What|Removed |Added

   Hardware|x86 |All
 OS|Windows |All

--

[Issue 13041] std.range.transposed consumes sub-ranges

2015-01-02 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13041

Peter Alexander  changed:

   What|Removed |Added

 CC||peter.alexander...@gmail.co
   ||m
Summary|A problem in|std.range.transposed
   |std.range.transposed|consumes sub-ranges

--

[Issue 13041] std.range.transposed consumes sub-ranges

2015-01-02 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=13041

Peter Alexander  changed:

   What|Removed |Added

 CC||hst...@quickfur.ath.cx

--- Comment #1 from Peter Alexander  ---
*** Issue 13824 has been marked as a duplicate of this issue. ***

--