Skip to content

Conversation

@xedin
Copy link
Contributor

@xedin xedin commented Oct 29, 2025

…ated` async function types

With the feature enabled any function type without an explicit @concurrent is going to be inferred to be nonisolated(nonsending). @concurrent should always be printed for diagnostic and other purposes because the isolation checking would consider them to be nonisolated(nonsending) otherwise, especially important to code produced by fix-its.

Resolves: rdar://161739470

@xedin
Copy link
Contributor Author

xedin commented Oct 30, 2025

@swift-ci please test

@xedin
Copy link
Contributor Author

xedin commented Oct 31, 2025

@swift-ci please test macOS platform

…ated` async function types

With the feature enabled any function type without an explicit `@concurrent`
is going to be inferred to be `nonisolated(nonsending)`. `@concurrent` should
always be printed for diagnostic and other purposes because the isolation
checking would consider them to be `nonisolated(nonsending)` otherwise, especially
important to code produced by fix-its.

Resolves: rdar://161739470
@xedin
Copy link
Contributor Author

xedin commented Nov 3, 2025

@swift-ci please test

@xedin xedin merged commit 3ce0f94 into swiftlang:main Nov 4, 2025
5 checks passed
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.

2 participants