Closing mapped streams - what's the idea?

后端 未结 1 1760
小蘑菇
小蘑菇 2021-02-14 02:43

It\'s well known that Javadoc says about Stream interface:

Streams have a BaseStream.close() method and implement AutoCloseable, but nearly all

1条回答
  •  无人及你
    2021-02-14 03:07

    The general rule about resource handling is that whoever is responsible for closing a resource is the one that opened it. The flatMap operation is the only operation in the Stream API that opens a Stream, so it is the only operation that will close it.

    Quoting from this mail, Brian Goetz said:

    To summarize, flatMap() is the only operation that internally closes the stream after its done, and for good reason -- it is the only case where the stream is effectively opened by the operation itself, and therefore should be closed by the operation too. Any other streams are assumed to be opened by the caller, and therefore should be closed by the caller.

    The example given is the following. Consider

    try (Stream paths = Files.walk(dir)) {
        Stream stream = paths.flatMap(p ->  {
            try {
                return Files.lines(p);
            } catch (IOException e) {
                throw new UncheckedIOException(e);
            }
        });
    }
    

    The method reference Files::lines returns a Stream of the lines of the file. When the flat mapping operation is over, it is expected that the opened resource used to read the file is closed. The question is: closed by what? Well, closed by flatMap itself because it is the operation that opened the Stream in the first place.

    Files.lines returns a Stream with a pre-registered close handler that closes the underlying BufferedReader. When the flatMap operation is done, this close handler is invoked and the resources are correctly released.


    The reason this idea is backported to flatMapTo* operations is the same: adhering to the above rule that every resource allocated by a process should be closed by that process.

    Just to show that you can build an IntStream which would have an underlying resource to close, consider the following Stream pipeline where each path is not flatmapped to its lines but to the number of character in each line.

    try (Stream paths = Files.walk(dir)) {
        IntStream stream = paths.flatMapToInt(p ->  {
            try {
                return Files.lines(p).mapToInt(String::length);
            } catch (IOException e) {
                throw new UncheckedIOException(e);
            }
        });
    }
    

    0 讨论(0)
提交回复
热议问题