AST/Sema: Introduce AvailabilityContext
#77083
Merged
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.
AvailabilityContext
is designed to be a compact representation of the active availability constraints in a specific scope. For now, it only models platform introduction availability but it will soon be updated to cover additional availability constraints, like platform unavailability.TypeRefinementContext
now represents availability constraints usingAvailabilityContext
instead of just anAvailabilityRange
representing only platform introduction versions. In anticipation of the memory requirements forAvailabilityContext
growing, a cache of uniqued instances ofAvailabilityContext
are stored in allvm::FoldingSet
onASTContext
.There should be no functional changes since this just changes the representation of the existing information stored by
TypeRefinementContext
. However, in the futureAvailabilityContext
will be expanded to represent additional availability constraints.