@zackw Good that you bring that up. @tmccombs’s proposal proposes a call style similar to method calls, but leaves the . method call syntax itself as it works today. Consequently similar precedence as . is intended. |> suggests low precedence, doesn’t it? That’s unintuitive if it actually isn’t intended to be low precedence.
Your use case can be implemented with an iterator and functional programming. Or, if your dataset is large using a parallel iterator from rayon. This syntax (with precedence similar to .) is intended to be quite useful for iterators. @Centril came up with the whole controversial idea about changing the method call syntax because it would be useful for crates like itertools in this post (I think that’s where the idea first popped up).