Shouldn't iterator be called something else – e.g. operation?

[behrangsa]

In:

each(arr, iterator, [callback])

The second argument is not the iterator. each itself is the iterator. The second argument is an operation that the iterator perform on each and every member of the passed array, arr.

Am I missing something here?

[aearly]

Our nomenclature is a bit weird. All these examples predate the official iterator spec. It's hard to pick a better word --- taskFn, operation, asyncFn, iteratingFn, etc...

To make things more confusing, we're going to add support for ES6 iterators in addition to plain arrays for functions like each. And then there's the async function () {} syntax on the horizon...

[megawac]

iteratee is the technically correct term

[aearly]

The benefits of having a contributor who still remembers his CS! Should we change the docs across the board to use iteratee?

[behrangsa]

I would say yes, let's use iteratee.

[crispen-smith]

For what its worth +1, Aldo please let me know if I can help with this change.

[megawac]

@crispen-smith make the pull request if interested otherwise me or Alex will whenever we have some spare time

[crispen-smith]

I'll submit in the next few days.

[crispen-smith]

PR Submitted.

[aearly]

Closed via #1021