[5.8 🍒] TypeCheckType: Fix existential any
migration diagnostics for extra-modular protocols
#65160
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.
I’m attempting to bring this fix to 5.8 because the issue negatively affects piecemeal adoption of existential
any
syntax (--enable-upcoming-feature ExistentialAny
) — a Swift 6 feature with substantial source impact — in that the syntax is not enforced on standard library existentials such asError
andCodable
. More generally, any existential that has a native imported constraint type and is normally allowed to omitany
in Swift 5.any
migration diagnostics for extra-modular protocols #65112.any
in Swift 6 mode.ExistentialAny
does not work for standard library protocols. #65034.ExistentialAny
feature is enabled (enabling the feature is supposed to be source-breaking).any
migration diagnostics for extra-modular protocols #65112