[GR-63268] Do not require negative queries for impossible class names #11240
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 typesfully.qualified.ClassName$InnerClassName
for nested typesUnder
--exact-reachability-metadata
, any class name that doesn't fit these will now throw aClassNotFoundException
even if the corresponding query wasn't registered. This should reduce reachability metadata size for users doing a lot of reflective poking.