--- Comment #4 from deadalnix <> 2012-10-16 14:20:32 PDT ---
(In reply to comment #3)
> (In reply to comment #2)
> > Being unable to do .map.filter defeat the whole point of map and filter.
> Sorry, I'm not following. Why are you saying you can't do a .map.filter? You
> can, it just calls the map function more than once per element.
> What exactly is the problem?

The problem is that the delegate get executed an impredictable number of time.
Which make side effect extremely hard to handle (I ended up using
map.array.filter most of the time in my own codebase) in terms of side-effect
or performance.

Additionally, the problem is dependent of the inner implementation of both map
and filter, which should stay unknown for the user.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to