Sema: Check the availability of conformance type witnesses #75938
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@swift-ci please test |
|
@swift-ci please test source compatibility |
slavapestov
reviewed
Aug 17, 2024
tshortli
force-pushed
the
associated-type-witness-availability
branch
from
2824391 to
189c1d3
Compare
|
@swift-ci please smoke test |
Code that wants to determine whether a given declaration should be considered unavailable should use this new utility, which will take the unavailability of the context of use into consideration. NFC.
The type satisfying a protocol requirement must be at least as available as the associated type for the requirement. Resolves rdar://134093006
tshortli
force-pushed
the
associated-type-witness-availability
branch
from
d002bb8 to
4420ea8
Compare
|
@swift-ci please smoke test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The type satisfying a protocol requirement must be at least as available as the associated type for the requirement. This has always been a potential soundness hole that should have been checked, but it is especially important to diagnose these issues now that associated type requirements can have their own availability (#70735). Unfortunately, these diagnostics cannot be introduced as errors since doing so would break source compatibility for existing libraries so for now they are staged as warnings until a post Swift 6 language mode is available.
Resolves rdar://134093006.