On Wed, 25 Feb 2026 06:17:45 GMT, ExE Boss <[email protected]> wrote: >> On the contrary, I think adding `final` here serves as a good indicator to >> anyone possibly wanting to override spliterator() that they need to consider >> the behavior of the superclass' implementation. AS EnumSet is `sealed` there >> is no risk to non-jdk code and dropping the `final`-modifier later is >> trivial. > > Changing `final`ness of a public method on a **JDK**‑`sealed` hierarchy still > requires a **CSR**, since it’s considered a part of the **JavaSE API** > specification.
Yes, that kind of change does require a CSR, but it is an easy review :-) ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/28696#discussion_r2875046372
