Skip to content

Gardening: AvailabilityContext and AvailabilityConstraint cleanup #79734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Mar 3, 2025

Conversation

tshortli
Copy link
Contributor

@tshortli tshortli commented Mar 2, 2025

  • Use const consistently for ASTContext parameters.
  • Rename Range to PlatformRange in AvailabilityContext::Info.
  • Rename a couple of AvailabilityConstraint::Reason cases. Choose names that don't imply availability is versioned, since custom availability will support domains that are version-less (they are simply available or unavailable).

@tshortli tshortli enabled auto-merge March 2, 2025 21:53
@tshortli tshortli force-pushed the availability-context-gardening branch from 0693930 to 2569705 Compare March 2, 2025 22:45
@tshortli
Copy link
Contributor Author

tshortli commented Mar 2, 2025

@swift-ci please smoke test

Choose names that don't imply availability is versioned, since custom
availability will support domains that are version-less (they are simply
available or unavailable).
@tshortli tshortli force-pushed the availability-context-gardening branch from 2569705 to dc2fe53 Compare March 2, 2025 23:09
@tshortli
Copy link
Contributor Author

tshortli commented Mar 2, 2025

@swift-ci please smoke test

@tshortli tshortli merged commit 974767e into swiftlang:main Mar 3, 2025
3 checks passed
@tshortli tshortli deleted the availability-context-gardening branch March 3, 2025 03:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant