There’s a reason why most examples avoid storing the result into a Collection. It’s not the recommended way of programming. You already have a Collection, the one providing the source data and collections are of no use on its own. You want to perform certain operations on it so the ideal case is to perform the operation using the stream and skip storing the data in an intermediate Collection. This is what most examples try to suggest.
Of course, there are a lot of existing APIs working with Collections and there always will be. So the Stream API offers different ways to handle the demand for a Collection.
-
Get an unmodifiable
Listimplementation containing all elements (JDK 16):List<T> results = l.stream().filter(…).toList(); -
Get an arbitrary
Listimplementation holding the result:List<T> results = l.stream().filter(…).collect(Collectors.toList()); -
Get an unmodifiable
ListforbiddingnulllikeList.of(…)(JDK 10):List<T> results = l.stream().filter(…).collect(Collectors.toUnmodifiableList()); -
Get an arbitrary
Setimplementation holding the result:Set<T> results = l.stream().filter(…).collect(Collectors.toSet()); -
Get a specific
Collection:ArrayList<T> results = l.stream().filter(…).collect(Collectors.toCollection(ArrayList::new)); -
Add to an existing
Collection:l.stream().filter(…).forEach(existing::add); -
Create an array:
String[] array=l.stream().filter(…).toArray(String[]::new); -
Use the array to create a list with a specific specific behavior (mutable, fixed size):
List<String> al=Arrays.asList(l.stream().filter(…).toArray(String[]::new)); -
Allow a parallel capable stream to add to temporary local lists and join them afterward:
List<T> results = l.stream().filter(…).collect(ArrayList::new, List::add, List::addAll);(Note: this is closely related to how
Collectors.toList()is currently implemented, but that’s an implementation detail, i.e. there is no guarantee that future implementations of thetoList()collectors will still return anArrayList)