I wonder should the CSR not describe what’s the advantage of this change is and what the compatibility problems are and why they don’t apply here? Especially given the fact that the specific sub exceptions are not sealed I wonder if the risk of breaking existing code is worth it? (But I do see the beauty of such a construct for new code!)
Gruss Bernd -- http://bernd.eckenfels.net ________________________________ Von: core-libs-dev <[email protected]> im Auftrag von Jaikiran Pai <[email protected]> Gesendet: Friday, March 25, 2022 10:27:40 AM An: [email protected] <[email protected]> Betreff: Re: RFR: JDK-8283668: Update IllegalFormatException to use sealed classes On Fri, 25 Mar 2022 04:17:57 GMT, Joe Darcy <[email protected]> wrote: > Working down the list of candidates to be sealed, this time > IllegalFormatException. > > Please also review the companion CSR: > https://bugs.openjdk.java.net/browse/JDK-8283669 Marked as reviewed by jpai (Committer). ------------- PR: https://git.openjdk.java.net/jdk/pull/7950
