rschmitt at pobox.com
Mon Oct 14 22:45:52 UTC 2019
I commonly encounter older APIs that throw checked exceptions. There
are two ways in which this is inconvenient. One is that I have to
wrap-and-throw the exception as a RuntimeException. The other is that
methods that throw checked exceptions are (practically speaking)
incompatible with method references, because the majority of
@FunctionalInterface types don't throw any checked exceptions.
I'm curious to know what the current thinking is on checked
exceptions. Is there agreement that the current situation is less than
ideal? If so, how might they be addressed, and are they even enough of
a problem to be worth addressing?
More information about the jdk-dev