A terminal operation is the deliberate stopping point of a functional pipeline: it triggers deferred processing and materializes the final result. Without it, stream creation, filtering, and mapping describe behavior but process no data. section 6.3.1 section 6.5
Use terminal operations as the pipeline’s final action:
- Choose one terminal operation after any number of intermediate operations, including none. section 6.3.1
- Expect execution to begin only when operations such as toList, collect, or count are applied. section 6.5
- Treat the consumed pipeline as finished; it cannot be reused after termination. section 6.3.1
Materializing recent authors
A stream can filter recently published books and map them to author names, but the result becomes a List only at the final toList() call. The terminal operation turns a readable transformation description into executed output. section 6.3.1
