@utkarshkukreti Thanks for the suggestion, but these special cased each methods feel like they should be in their own extension, _.mixin. I'll defer to Underscore's reason for not adopting it.

Extensions like this will be easier to put together when we provide pre-sliced AMD/CommonJS/Node modules in the next major bump.

I know this is an old request, but I would really like to understand the rationale behind these rejections. I mean, almost everything in this library is a fold (or reduce) special case. And chunk is nothing but this, with a stride equal to its length. How's this (and underscore's) request any different from having chunk?

Just as an FYI to anybody else searching for functionality similar to Ruby's eachCons, Ramda has this functionality named as aperture.

in Kotlin, i believe this is called windowed(n). Maybe a quick way to do this without a new function is to drop one element first and use the rest to go through the index.

https://stackoverflow.com/a/48541301/2180570

const zipAdjacent = function<T> (ts: T[]): [T, T][] {
  return zip(dropRight(ts, 1), tail(ts));
};

by Oliver Joseph Ash

https://stackoverflow.com/a/67602261/2180570

const pairWise = a => a.slice(1).map((k,i) => [a[i], k]);

by loop