[Issue 17741] std.range.transposed does not work with Map

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

Alexandru Razvan Caciulescu  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #4 from Alexandru Razvan Caciulescu  
---
Decided to close this issue. The simple workaround is to use:
auto result = ror.array.transposed;

--


[Issue 17741] std.range.transposed does not work with Map

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

Alexandru Razvan Caciulescu  changed:

   What|Removed |Added

 CC||alexandru.razva...@gmail.co
   ||m

--- Comment #2 from Alexandru Razvan Caciulescu  
---
Created a PR for this. I had to change a test for issue #8764
https://issues.dlang.org/show_bug.cgi?id=8764
However I checked and it's not introducing any regression.

--


[Issue 17741] std.range.transposed does not work with Map

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

--- Comment #3 from Alexandru Razvan Caciulescu  
---
https://github.com/dlang/phobos/pull/5810

--


[Issue 17741] std.range.transposed does not work with Map

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

RazvanN  changed:

   What|Removed |Added

 CC||razvan.nitu1...@gmail.com

--- Comment #1 from RazvanN  ---
What should be the solution here? Implement an overload which accepts a range
with non-assignable elements and returns a range with non-assignable elements
or offer the illusion of assign-ability by implementing a hashtable on top of
transpose which tracks the changes performed in the initial range?

--