Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Passing an
Object[]as the array argument to typed Java varargs currently treats the entire array as one vararg element. Calls such asClass.getDeclaredMethod(..., (Object[]){...})then try to castObject[]to the component type instead of converting its elements to the declared array type.Recognize a non-null
Object[]in the fixed-arity position after member selection, convert its elements with the existing coercion rules, and invoke the member with the declared varargs array type. Already typed arrays, null arrays, and expanded varargs keep their existing behavior, while anonymous subclasses apply the same conversion before forwarding arguments to a typed-varargs superclass constructor. Method overload selection remains unchanged.