[Features] Update upcoming feature flags for Swift 6. #70123
Merged
Conversation
This file contains 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
hborla
requested review from
ktoso,
kavon,
slavapestov,
xedin and
tshortli
as code owners
|
@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.
Changes and additions to upcoming feature flags for Swift 6 as described in https://forums.swift.org/t/progress-toward-the-swift-6-language-mode/68315.
ExistentialAnyby default in Swift 6.StrictConcurrencyexperimental feature flag, which was added so that packages can take advantage of-strict-concurrency=complete. Note that the upcoming feature flag is under a new name (CompleteConcurrency) and theStrictConcurrencyexperimental feature flag is still intact so that existing uses of-enable-experimental-feature StrictConcurrencycontinue to enable complete concurrency checking.