Skip to content
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

Jump to bottom

[SR-15235] Report warnings about the use of escaping closures with actor-isolated assumption #57557

Closed
kateinoigakukun opened this issue Sep 23, 2021 · 2 comments
Closed

[SR-15235] Report warnings about the use of escaping closures with actor-isolated assumption #57557

kateinoigakukun opened this issue Sep 23, 2021 · 2 comments
Labels
compiler The Swift compiler in itself concurrency Feature: umbrella label for concurrency language features improvement

Comments

@kateinoigakukun
Copy link
Member

Previous ID SR-15235
Radar rdar://problem/83455925
Original Reporter @kateinoigakukun
Type Improvement
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 1
Component/s Compiler
Labels Improvement, Concurrency
Assignee None
Priority Medium

md5: 65f92cbf864228ca02ef3a8ba8e13788

Issue Description:

Since this commit, non-sendable escaping closure can be used as actor-isolated.

5ecb9eb

But this assumption is apparently unsafe as the commit message said.

If this restriction is planned to be restored in Swift 6, the compiler should report warnings about this when `-warn-concurrency` is given.
@typesanitizer
Copy link

@swift-ci create

@DougGregor
Copy link
Member

Sendable checking has been enabled for the upcoming Swift 5.6. There are a number of changes involved, but #40442 is one of the more recent ones.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler The Swift compiler in itself concurrency Feature: umbrella label for concurrency language features improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DougGregor @typesanitizer @kateinoigakukun