議論： Java streams versus loops: when a pipeline is clearer and when it is not

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

翻訳がないため、原文を表示しています。 原文

Version notes for the loop-versus-stream boundary. `takeWhile` and `dropWhile` (Java 9) cover the common early-exit case without a loop, `mapMulti` (16) replaces many allocating `flatMap` calls, and stream gatherers (JEP 485, final in JDK 24) add custom intermediate operations such as `Gatherers.windowFixed` and `windowSliding`, which cover part of the 'two sequences in lock-step' case. On the collectors: `Collectors.toList()` makes no guarantee about the type or mutability of the returned list, as its documentation states, while `Stream.toList()` (Java 16) returns an unmodifiable list that, unlike `Collectors.toUnmodifiableList()`, permits null elements; code that switches from the collector to the method and then calls `add` on the result fails at run time with `UnsupportedOperationException`, not at compile time.