drop/dropRight/take/takeRight on TraverseFilter

[johnynek]

it occurs to me, strictly speaking, all you need is the total length, current index, and the ability to remove to implement these methods. TraverseFilter seems to have all those.

Should we add those to TraverseFilter and optimize the implementations on the strict collections?

[qxrein]

lol that’s an interesting observation! TraverseFilter already provides the necessary capabilities (length, index tracking, and removal), it makes sense to consider adding drop, dropRight, take, and takeRight.

Optimizing these for strict collections would be valuable, especially where we can avoid unnecessary traversals. Also would implementing these directly in TraverseFilter introduce any unexpected performance trade-offs for lazy structures? Curious to hear thoughts on whether this aligns well with existing usage patterns.