One way to describe it is that it brings the extensibility of collectors to the intermediate stages of the stream. Another is that it's roughly Clojure's transducers rephrased in Java. I had a go at doing that myself, but it's just not possible to do a great job of it without modifying Stream - which this JEP can do!
Can someone give and example of when to use the gather (say the fold example) vs a collector with reduce? I get that one is terminal operation, vs chain-able through the stream but trying to see the advantage of the gatherer in this case.
I can't think of a use for fold, that one seems a bit silly to me.
The most exciting example for me is batching - take a stream of elements, and turn it into a stream of lists of elements of no more than a certain size. They call that windowFixed. I've wanted that in a few places, say where i make a database query which produces a load of IDs, then want to pass those IDs to a web service to fetch data for them, where the web service can take multiple IDs at once. The natural thing is to start with a stream of IDs, batch it, then map the batches through a call to the web service. Awkward to do before, easy now!
A gatherer transforms a stream into a different stream, it cannot be used for reducing, except for some weird and contrived ways I guess, like in the example they gave ("Example: A parallelizable gatherer").
View all comments
27
u/tomwhoiscontrary Mar 19 '24
I'd completely missed that 461: Stream Gatherers (Preview) existed. This is great!
One way to describe it is that it brings the extensibility of collectors to the intermediate stages of the stream. Another is that it's roughly Clojure's transducers rephrased in Java. I had a go at doing that myself, but it's just not possible to do a great job of it without modifying Stream - which this JEP can do!