Consider re-writing util-functions Iterables::any, all, forEach, etc. without resorting to Java Streams but rather using Iterator's forEachRemaining and direct for-loops. Some argue that creating Streams strangles performance.
We need to write some performance tests. In particular, the above assertions about the performance issues with Streams-based loops might ignore the one-off performance overhead when creating lambdas for the first time. Maybe, the performance is comparable once the lambdas are created.
Consider re-writing util-functions
Iterables::any, all, forEach, etc. without resorting to Java Streams but rather using Iterator'sforEachRemainingand direct for-loops. Some argue that creating Streams strangles performance.We need to write some performance tests. In particular, the above assertions about the performance issues with Streams-based loops might ignore the one-off performance overhead when creating lambdas for the first time. Maybe, the performance is comparable once the lambdas are created.