>> isPredictableSplits // can always return false > > Is there any potential use that is not covered by > knowing min/max of current and subtask splits? Yes. The idea here is that the spliterator knows its split sizes *all the way down*. Which means that you can go straight to direct packing / indexing at the leaves.