AST: Retire subclasses of AvailabilitySpec
#79354
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.
Consolidate everything that
AvailabilitySpec
models into a single class, instead of having subclasses that model each flavor of spec. Soon, anAvailabilitySpec
will only carry the raw availability domain identifier as a parsed string and the availability domain instance will need to be queried using a request that takes aDeclContext
, so we will not be able to distinguish between flavors of spec during parsing. Most availability spec related diagnostics will need to move from parsing to type checking.Builds on #79312.
NFC.