Support superclass annotations when deciding whether a class should be isolated. #3441
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.
This is a suggested change to improve behavior of
@Isolate
annotation.Context
At the moment, the
@Isolate
annotation on the parent class does not affect the isolation of child classes in any way.Changes
These changes will help make annotation search customizable as needed.
AnnotationSearchParameter
IncludingAnnotations
andIncludingSuperclasses
Reflection#annotations
now accept a set of AnnotationSearchParameter insteadrecursive
flagKClass<*>#annotations
andKClass<*>#hasAnnotation
by default still has just recursive behaviorKClass<*>#isIsolate
in addition to recursive check, checks the presence of@DoNotParallelize
or@Isolate
in superclassesPair<KClass<*>, Set<AnnotationSearchParameter>