is there any reason that array checking for _.each goes off of presence of .length?

[mbriggs]

Helped a co-worker this morning try to figure out why _.each wasn't working for his object (which happened to have a length field on it). There are several ways to check for arrays that I know of (Object.prototype.toString, checking constructor), is there any reason that the choice was made to go for .length?

[jashkenas]

Yep -- so that we support both arrays and array-like objects: arguments, NodeLists, and so on.

[jdalton]

@mbriggs I've addressed this with _.forIn and _.forOwn. Lemme know if that works for ya.