On Thu, 12 Mar 2026 23:50:01 GMT, Chen Liang <[email protected]> wrote:
>> Currently, the preview access flag enum constants are made available with a >> ClassFileFormatVersion.CURRENT_PREVIEW_FEATURES constant. Such a constant is >> questionable design. >> >> We can have an approach to model preview access flags without such a >> constant, losing the ability for users to inspect through >> `ClassFileFormatVersion`, but otherwise keeping these interfaces intact: >> >> 1. `accessFlags()` factory methods in core reflection >> 2. Inspection of AccessFlag through ClassFile API >> 3. The outputs of javap >> >> The new design makes use of a new internal API, >> `jdk.internal.reflect.PreviewAccessFlags`. It replaces the AccessFlag APIs >> that previously took `ClassFileFormatVersion.CURRENT_PREVIEW_FEATURES`. This >> introduces a new qualified export from `java.base/jdk.internal.reflect` to >> `jdk.jdeps` for Javap usage. >> >> In addition, with the recent awareness that core reflection/HotSpot only has >> one unique representation of modifiers, we can remove some contrived >> representation of access flags present in mainline (that required pulling >> class version from Class mirrors) and migrate to our simplified system that >> decodes the uniform representation used by hotspot. > > Chen Liang has updated the pull request incrementally with one additional > commit since the last revision: > > Factor out AccessFlagSet to be used by Reflection.modifiersToFlags Did another refactor: Moved `AccessFlagSet` to a top-level class in jdk.internal to enable its use by `Reflection.modifiersToFlags`, massively simplifying some old STRICT hack code. ------------- PR Comment: https://git.openjdk.org/valhalla/pull/2209#issuecomment-4051165464
