-
Notifications
You must be signed in to change notification settings - Fork 10.5k
TypeCheckType: Unconditionally warn about missing existential any
until a future language mode
#78459
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
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
d88507b
to
4dfd064
Compare
any
until Swift 7any
until Swift 7
@swift-ci please smoke test macOS |
4dfd064
to
ce9c54c
Compare
@swift-ci please smoke test macOS |
…ntil Swift 7 swiftlang#72659 turned out to have some source compatibility fallout that we need to fix. Instead of introducing yet another brittle compatibility hack, stop emitting errors about a missing `any` altogether until a future language mode. Besides resolving the compatibility issue, this will encourage developers to adopt any sooner and grant us ample time to gracefully address any remaining bugs before the source compatibility burden resurfaces. A subsequent commit adds a diagnostic group that will allow users to escalate these warnings to errors with `-Werror ExistentialAny`.
ce9c54c
to
b739918
Compare
any
until Swift 7any
until Swift 7
b739918
to
966ea4b
Compare
Allow users to escalate `any` syntax warnings to errors with `-Werror ExistentialAny`.
966ea4b
to
3222053
Compare
@swift-ci please smoke test |
@swift-ci please test source compatibility release |
slavapestov
approved these changes
Feb 13, 2025
@swift-ci please smoke test Windows |
penny-bot failure unrelated. |
@swift-ci please smoke test Linux |
any
until Swift 7any
until a future language mode
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.
#72659 turned out to have some source compatibility fallout that we need to fix. Instead of introducing yet another brittle compatibility hack, stop emitting errors about a missing
any
altogether until a future language mode.Besides resolving the compatibility issue, this will encourage developers to adopt
any
sooner and grant us ample time to gracefully address any remaining bugs before the source compatibility burden resurfaces.Users can still escalate these warnings to errors with
-Werror ExistentialAny
.