Thanks for pointing this out. We don't use parallel streams for the
cases in question, so we don't have the concurrency concerns that the
stream docs point out. However, we should take a look and make sure that
the call to peek can't be optimized out, since I expect some
applications will start
Hey all,
recently I stumbled over the problem of non-executing stream operations,
especially `Stream.peek(Consumer action)`, for more Info see [1].
With JDK 17 this behaviour is even extended (e.g. skip() preserves the SIZED
attribute of a stream, making optimizations possible).
Out of curiosi
