Skip to content

[GR-63268] Do not require negative queries for impossible class names #11240

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

graalvmbot
Copy link
Collaborator

Removes the need to register class lookups for Class.forName queries if the class name can't possibly be a Java class name. Such a name can only have the following formats:

  • fully.qualified.ClassName for regular classes
  • [Lfully.qualified.ClassName; for array types
  • fully.qualified.ClassName$InnerClassName for nested types

Under --exact-reachability-metadata, any class name that doesn't fit these will now throw a ClassNotFoundException even if the corresponding query wasn't registered. This should reduce reachability metadata size for users doing a lot of reflective poking.

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label May 21, 2025
@graalvmbot graalvmbot force-pushed the lottet/GR-63268-reduce-negative-queries branch from 63d9317 to 7fc30ab Compare May 22, 2025 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants