Avoid multiple volatile reads/writes in a row where only one is enough #25899
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.
MethodInvocationProceedingJoinPoint
use the same approach as inInjectionPoint.getAnnotations()
to do only one volatile read for all calls after field initialization instead of two.AutowiredAnnotationBeanPostProcessor
we are guareded bysynchronized
AbstractCacheManager
newly createdLinkedHashSet
always has some extra capacity, so calculation of it's size +1 is redundant