2531655 oop.dispatch public

[jafl]

No description provided.

[travisbot]

This pull request passes (merged a8052c7 into aa2d5e6).

[sdesai]

Thanks. Will look at pulling this in.

[sdesai]

Putting into the backlog for the next sprint, starting 9/25/12

[tilomitra]

Hey @jafl, after looking through the discussion on this ticket, I think the best fix here is to make sure Y.Array.each supports NodeLists and ModelLists. This sounds like a better fix than using Y.each and Y.some generically (as mentioned in the thread).

I'll close this for now. Feel free to create a ticket asking for Y.Array.each support for NodeLists and ModelLists. I think that makes sense.

[jafl]

Please reconsider.

The point of this pull request was not specifically Y.each. The point was to expose a method that can be used to implement all the functions like Y.map, Y.filter, Y.reject, Y.partition, etc.

From my comments in the ticket:

While I agree that in some cases, iteration may matter for Y.some, Y.every, and Y.reduce, the whole point of Y.each, Y.map, Y.filter, Y.reject, Y.partition is that iteration order is irrelevant. They are trivially parallelizable -- no matter that JavaScript is single threaded.