Skip to main content

TIL: Stream.toList() vs Collectors.toList() in Java

· 2 min read
Kavinda Dewmith
Kavinda Dewmith
Software Engineer

Java 16 introduced Stream.toList() as a shorter way to collect a stream into a list. Looks like a simple convenience method — turns out there's a meaningful difference.

Context​

I was simplifying some stream pipelines and swapped collect(Collectors.toList()) for the newer Stream.toList(). Tests started failing with UnsupportedOperationException. Not obvious why at first.

The discovery​

Stream.toList() returns an unmodifiable list. Collectors.toList() returns a regular mutable ArrayList.

// Collectors.toList() — mutable, you can add/remove after
List<String> mutable = stream.collect(Collectors.toList());
mutable.add("extra"); // fine

// Stream.toList() — unmodifiable
List<String> immutable = stream.toList();
immutable.add("extra"); // throws UnsupportedOperationException

Collectors.toUnmodifiableList() existed before Java 16 and gives the same behaviour as Stream.toList() — so the new method is really a shorthand for the unmodifiable version, not the mutable one.

Why it matters​

If you're collecting into a list you then mutate (sorting in place, removing elements, etc.), the new shorthand will break. The fix is straightforward — use Collectors.toList() when you need mutability, Stream.toList() when you don't — but the failure mode is a runtime exception, not a compile error.

Prefer Stream.toList() by default (immutability is usually the right default), and reach for Collectors.toList() only when you need to mutate the result.

Source​