Skip to content

Add StrictConcurrency as an always-enabled experimental feature#66991

Merged
DougGregor merged 1 commit intoswiftlang:mainfrom
DougGregor:experimental-feature-strict-concurrency
Jun 28, 2023
Merged

Add StrictConcurrency as an always-enabled experimental feature#66991
DougGregor merged 1 commit intoswiftlang:mainfrom
DougGregor:experimental-feature-strict-concurrency

Conversation

@DougGregor
Copy link
Member

Upcoming and experimental features are supported via command-line flags and also in the SwiftPM manifest. Introduce it as an experimental feature so that it can be enabled via SwiftPM without having to resort to unsafe flags.

The StrictConcurrency experimental feature can also provide a strictness level in the same manner as -strict-concurrency, e.g., StrictConcurrency=targeted. If the level is not provided, it'll be complete.

Note that we do not introduce this as an "upcoming" feature, because upcoming features should be in their final "Swift 6" form before becoming available. We are still tuning the checking for concurrency.

Upcoming and experimental features are supported via command-line flags
and also in the SwiftPM manifest. Introduce it as an experimental
feature so that it can be enabled via SwiftPM without having to resort
to unsafe flags.

The `StrictConcurrency` experimental feature can also provide a
strictness level in the same manner as `-strict-concurrency`, e.g.,
`StrictConcurrency=targeted`. If the level is not provided, it'll be
`complete`.

Note that we do not introduce this as an "upcoming" feature, because
upcoming features should be in their final "Swift 6" form before
becoming available. We are still tuning the checking for concurrency.
@DougGregor
Copy link
Member Author

@swift-ci please smoke test

@DougGregor
Copy link
Member Author

@gwynne I stole your commits so I could turn around a quick fix, thank you!

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.

3 participants