|
|
|
|
|
|
by pron
579 days ago
|
|
|
As part of our "integrity by default" strategy [1] we're changing that. There will be a JEP about it soon. The idea is that because not much code actually needs to mutate finals (and even if it does, that operation is already limited today to classes in the code's own modules or ones explicitly "open" to it), the application will need to grant a permission to a module that wants to mutate finals, similar to how we've recently done things with native calls and unsafe memory access. [1]: https://openjdk.org/jeps/8305968 |
|
|