Java 8 officially introduce java.io.UncheckedIOException to JDK class libraries for lambda with Stream API, because lambda expressions can't declare its throws-clause and lambda body can't throw checked exception such as IOException.
What's idiom/best practice with UncheckedIOException and Stream API? What conditions do I explicitly throw new UncheckedIOException object, and when should I catch UncheckedIOException exception?
You would throw it in the same circumstances as the library methods (BufferedReader.lines and Files.lines) that currently do it: that is, when you are wrapping an I/O exception resulting from an operation subsequent to opening a file (file opening operations still throw IOException). As for catching it, that depends on your strategy for IO error recovery: in other words, do whatever you do to handle the wrapped IOException in non-stream code.
UncheckedIOException ASAP and rethrow as checked exception(IOException) within Stream API caller method. What do you think of this point?
IOException if that is what your method would do anyway, or else handle the IOException if that is what your method would do. PS. Is the answer accepted?
IOExceptions, but only if the interface method they are representing does so as well.java.util.function.Consumer<T>forStream#forEach()...