limit with Infinite Streams
You'll learn why limit is essential for working with infinite streams like Stream.iterate() and Stream.generate().
The Core Problem
Infinite streams, by definition, never end. If you try to process one without limiting it, your program will run forever (or until you run out of memory). The limit operation is the circuit breaker that makes infinite streams practical and safe.
How limit Saves the Day
When you apply limit(n) to an infinite stream, you're telling Java: "I only want the first N elements from this endless sequence." Because limit is a short-circuiting operation, the stream pipeline stops producing elements once it reaches your specified count—even though the source could theoretically continue forever.
// Without limit: this would run forever
// Stream.iterate(1, n -> n + 1).forEach(System.out::println); // DON'T DO THIS
// With limit: safe and finite
Stream.iterate(1, n -> n + 1)
.limit(5)
.forEach(System.out::println);
// Output: 1, 2, 3, 4, 5
// Generating random numbers infinitely
Stream.generate(Math::random)
.limit(3)
.forEach(System.out::println);
// Prints 3 random numbers, then stops
The Safety Net Analogy
Think of an infinite stream like a waterfall that never stops flowing. The limit operation is like placing a bucket underneath—it catches exactly the amount you need, then you walk away. Without the bucket, you'd stand there forever trying to collect water.
Key Takeaway: limit is not optional for infinite streams—it's mandatory. It transforms an endless sequence into a finite, processable collection of elements by short-circuiting the pipeline after N items.