While throwing an IOException added in commit 6813db0716995a93ed1811775b7ff518387aa1cb is the "right" thing to do, it breaks users code and examples because it requires that the user catch the exception.
It would be less breaking to change it to a runtime exception now, so that code crashes but with a useful stack trace, and then next year make it an IOException.
While throwing an IOException added in commit 6813db0716995a93ed1811775b7ff518387aa1cb is the "right" thing to do, it breaks users code and examples because it requires that the user catch the exception.
It would be less breaking to change it to a runtime exception now, so that code crashes but with a useful stack trace, and then next year make it an IOException.