Repository navigation
Ignore nested type annotations when computing variable nullability. - #2908
Open
copybara-service[bot] wants to merge 1 commit into
Open
copybara-service[bot] wants to merge 1 commit into
copybara-service[bot] wants to merge 1 commit into
Conversation
`hasNullabilityAnnotation` scanned all type attributes of a variable, so annotations on nested positions (e.g. `List<@nullable String>` or `@Nullable String[]`) made the variable itself nullable. Only the top-level annotations of the variable type are considered now, as is already done for method return types. PiperOrigin-RevId: 1014136548
This branch has not been deployed
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.
Ignore nested type annotations when computing variable nullability.
hasNullabilityAnnotationscanned all type attributes of a variable, soannotations on nested positions (e.g.
List<@Nullable String>or@Nullable String[]) made the variable itself nullable. Only the top-levelannotations of the variable type are considered now, as is already done for
method return types.