On Tue, 8 Mar 2022 11:45:13 GMT, Athijegannathan Sundararajan <sun...@openjdk.org> wrote:
> Do we need a CSR as a public class is changed from non-sealed to sealed? > > (Although the constructor has been package-private and hence it will not > affect any non-dk code as noted by Jaikiran via private conversation. Only > reflection will be able to see the difference of non-sealed to sealed change). Yes there should be a CSR(see: https://bugs.openjdk.java.net/browse/JDK-8282131 as an example) for this issue. ------------- PR: https://git.openjdk.java.net/jdk/pull/7741
