Skip to content

Sema: Skip diagnosing witness availability for unavailable conformances #79537

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

Conversation

tshortli
Copy link
Contributor

@tshortli tshortli commented Feb 21, 2025

If a conformance is unavailable then checking for the potential unavailability of a witness doesn't make sense so skip it. This is necessary now because availability scopes no longer constrain the platform introduction version for a source range in that is annotated in source to be simultaneously unavailable and also introduced in a later version.

This fixes a regression caused by #79249.

Resolves rdar://145255592.

If a conformance is unavailable then checking for the potential unavailability
of a witness doesn't make sense so skip it. This is necessary now because
availability scopes no longer constrain the platform introduction version for a
source range in that is annotated in source to be simultaneously unavailable
and also introduced in a later version.

This fixes a regression caused by swiftlang#79249.

Resolves rdar://145255592.
@tshortli tshortli force-pushed the potentially-unavailable-witness-in-unavailable-conformance branch from cc8b71c to 54e6900 Compare February 21, 2025 06:42
@tshortli
Copy link
Contributor Author

@swift-ci please test

@tshortli tshortli merged commit 205bfee into swiftlang:main Feb 21, 2025
5 checks passed
@tshortli tshortli deleted the potentially-unavailable-witness-in-unavailable-conformance branch February 21, 2025 15:52
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