http://d.puremagic.com/issues/show_bug.cgi?id=8155
Joseph Rushton Wakeling <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |t --- Comment #8 from Joseph Rushton Wakeling <[email protected]> 2013-06-28 06:19:31 PDT --- (In reply to comment #0) > I suggest to deprecate std.range.lockstep because with the recent improvements > in tuple unpacking, std.range.zip is able to replace its the main purpose There are currently some things that work with lockstep that don't with zip. Consider: auto arr1 = new double[10]; foreach(i, ref x; zip(iota(10), arr1)) { x = i; } writeln(arr1); auto arr2 = new double[10]; foreach(i, ref x; lockstep(iota(10), arr2)) { x = i; } writeln(arr2); The first array will output all nan's, the second will have values set correctly. I imagine this is a bug, but it needs to be fixed before zip is a viable lockstep replacement. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
