-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Update code to prepare for nullness annotations in Guava. #3026
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't the result here be
null
now? In which case,getInternal
should also return a nullable value.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
auxFuture.set
is called in 2 places:complete
, where it's called with aT
completeExceptionallyOrCancel
, where it's called with aCancelled
(That appears to match this comment.)
It's true that
T
might be a nullable type in some cases, so the result might benull
. But that's OK: The result can benull
only if it came throughcomplete(result: T)
. And that can happen only in the case thatT
is a nullable type.Put another way,
complete
andgetInternal
combine to implement a system that accepts aT
and produces aT
. It just happens to store theT
as anAny?
in the meantime because it sometimes wants to store aCancelled
instead.More broadly: This PR shouldn't change any runtime behavior.
result: T
could always be a null value. But once Guava is fully annotated for nullness (maybe in Guava 32.0?), the existingauxFuture.set(result)
call will stop working: At that point, Kotlin will not only know thatresult: T
could be a null value but also know thatauxFuture.set
should not be called with a null value because its parameter type isAny
. This PR changesauxFuture
so thatauxFuture.set
accepts anAny?
and the code continues to compile. But it doesn't change the values that were already possible.