Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.13.0, 2.14.0
-
None
-
None
Description
This was a behavior breaking change, and an incorrect one to boot.
Operations that can have I/O errors should throw IOException if they can't directly handle the I/O error. UncheckedIOException is not a reasonable alternative.
A method that can neither handle nor throw IOException must not perform I/O operations.
It's worth noting that functional programming, not just in Java but in general, does not allow I/O. As soon as a method performs I/O, it's no longer a pure function and should not be written in a functional style.
Attachments
Attachments
Issue Links
- links to