[Issue 15357] Cannot call std.algorithm.iteration.each on the result of std.range.lockstep
    via Digitalmars-d-bugs 
    digitalmars-d-bugs at puremagic.com
       
    Thu Nov 19 05:24:41 PST 2015
    
    
  
https://issues.dlang.org/show_bug.cgi?id=15357
--- Comment #5 from ryan at rcorre.net ---
(In reply to monkeyworks12 from comment #0)
> 
> In my opinion lockstep's opApply should be deprecated outright and replaced
> with a range interface that returns a reference to a tuple of its arguments.
The problem with returning a tuple from front is losing the ability to modify
elements by ref. IIRC this is exactly what zip does. If we can return a tuple
through a range interface that allows modifying elements by ref, then I think
we could entirely deprecate lockstep in favor of zip.
--
    
    
More information about the Digitalmars-d-bugs
mailing list