On Tue, 3 Feb 2026 20:21:48 GMT, Matias Saavedra Silva <[email protected]>
wrote:
> Strict initialization is now indicated with the access flag `ACC_STRICT_INIT`
> in the JVMS and the VM implementation should follow. `ACC_STRICT` is
> currently used as a method modifier for strict floating-point semantics so
> this refactor will help to make both modifiers distinct. VM and Java code has
> to be updated to use the correct modifier. Verified with tier x-y tests.
src/java.base/share/classes/java/lang/reflect/Modifier.java line 220:
> 218: * {@code strict_init} modifier; {@code false} otherwise.
> 219: */
> 220: public static boolean isStrictInit(int mod) {
Is a Modifier method really appropriate or needed?
Modifier is used to describe modifiers in the source and there is no language
keyword for "strict init".
It is already defined in AccessFlag and that should be sufficient for the use
cases.
-------------
PR Review Comment:
https://git.openjdk.org/valhalla/pull/2025#discussion_r2761399646
