On Wed, 29 Mar 2023 09:03:58 GMT, Alan Bateman <al...@openjdk.org> wrote:
> > I thought the change would trigger a change in the public API as the > > modifiers are changed for the class. This would likely be picked up by > > compatibility checks and so, a CSR would be needed? > > It's not a compatibility issue but a CSR is needed to track the change to the > signature. Not that I disagree with this PR, but it would be interesting to see rationale for it in CSR. ------------- PR Comment: https://git.openjdk.org/jdk/pull/13221#issuecomment-1488804341
