The problem is solved. Question has been deleted
You didn't provide the source of your quote, so let me quote the javadoc to you:
Streams differ from collections in several ways:
- No storage. A stream is not a data structure that stores elements; instead, it conveys elements from a source such as a data structure, an array, a generator function, or an I/O channel, through a pipeline of computational operations.
- Functional in nature. An operation on a stream produces a result, but does not modify its source. For example, filtering a
Streamobtained from a collection produces a new
Streamwithout the filtered elements, rather than removing elements from the source collection.
- Laziness-seeking. Many stream operations, such as filtering, mapping, or duplicate removal, can be implemented lazily, exposing opportunities for optimization. For example, "find the first
Stringwith three consecutive vowels" need not examine all the input strings. Stream operations are divided into intermediate (
Stream-producing) operations and terminal (value- or side-effect-producing) operations. Intermediate operations are always lazy.
- Possibly unbounded. While collections have a finite size, streams need not. Short-circuiting operations such as
findFirst()can allow computations on infinite streams to complete in finite time.
- Consumable. The elements of a stream are only visited once during the life of a stream. Like an
Iterator, a new stream must be generated to revisit the same elements of the source.
In contrast, a
Collection is a container of objects (elements). You can't get (retrieve) an object from a collection unless the object was previously added to the collection.