Make AbstractFuture
use VarHandle
when available.
#7555
+209
−53
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.
Make
AbstractFuture
useVarHandle
when available.For now, this is only for the JRE flavor, not for Android.
Our not entirely great benchmarks suggest that this may actually improve performance slightly over the current
Unsafe
-based implementation. This matches my sense that alternatives toUnsafe
have gotten faster.There are plenty of other places in Guava that we use
Unsafe
, but this is a start.Also: I'm going to consider this CL to "fix" #6549, even though:
RELNOTES=n/a