foreach: $array, $isFirst, $isLast, $isEven, $isOdd, $next, $previous - #2415

Conceptually I think this is useful, but we'd need to make sure it's consistent with the fast-foreach API in tko (since folks may move back-and-forth); the tko API is more complex since it's O(c) until $index is accessed, then it becomes O(1). A similar set of accessors could add quite a bit of complexity to fast-foreach.

I wonder why you want to perform such code in the template rather than adding a filteredArray to your model:

model.filteredArray = ko.pureComputed(() => model.array.filter(el => el > 1))

I don't see a huge downside of adding an $array to the context inside a forEach but I wonder if this kind of code isn't bad practice and should be avoided anyways.

@bikeshedder: Thanks for jumping in with a great point that I agree with. However, the situation that inspired this pull request was a bit more complex than the simplified example provided here and while your suggestion could be applied to that situation too, filtering in the template itself in that particular case led to a more developer-friendly solution.

I just realized that with the addition of the let binding in 3.5.0-rc, the need for $array is greatly reduced.

For example...

<!-- ko let: { myFilteredArray: arr().filter(...) } -->
<ul data-bind="foreach: myFilteredArray">
  <!-- myFilteredArray is still in scope -->
</ul>
<!-- /ko --> 

(I haven't actually tested this exact code)