You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm sure this has been answered to hell and back again, but is there any reason behind not including the index when using .map(), .each(), etc methods? When going over an Array, it would be super-handy to have this information (and would more closely match the native Array.prototype.forEach() method).
I saw there was a PR on #168, but that never seemed to move forward from there (and was more for iterating over object keys).
I can understand the need to not break backwards compatibility, but any plans on including such functionality? Are there any outstanding PR's that I'm missing?
The text was updated successfully, but these errors were encountered:
I'm sure this has been answered to hell and back again, but is there any reason behind not including the index when using
.map()
,.each()
, etc methods? When going over an Array, it would be super-handy to have this information (and would more closely match the nativeArray.prototype.forEach()
method).I saw there was a PR on #168, but that never seemed to move forward from there (and was more for iterating over object keys).
I can understand the need to not break backwards compatibility, but any plans on including such functionality? Are there any outstanding PR's that I'm missing?
The text was updated successfully, but these errors were encountered: