http://d.puremagic.com/issues/show_bug.cgi?id=4264
David Simcha <dsim...@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dsim...@yahoo.com --- Comment #6 from David Simcha <dsim...@yahoo.com> 2010-08-21 19:41:25 PDT --- Since everything you mention except the opApply issue is fixed either in 2.048 or in SVN, and the discussion has moved beyond Map to std.algorithm/std.range in general, I've changed the name of this bug. I've thought about supporting opApply in some std.range and std.algorithm types. I think it's useful and conceptually feasible (ignoring implementation minutiae) for at least the following, and probably more: std.algorithm.map std.algorithm.filter std.algorithm.uniq std.algorithm.until std.range.chain std.range.retro (if your object defines opApplyReverse) std.range.stride std.range.cycle It's definitely not feasible for anything that requires random access or manipulating multiple ranges in lockstep. I also don't see how to do it for std.range.splitter -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------