mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
3f6a0ccb90
It's ok to drop the global-actor qualifier `@G` from a function's type if:
- the cast is happening in a context isolated to global-actor `G`
- the function value will not be `@Sendable`
- the function value is not `async`
It's primarily safe to drop the attribute because we're already in the
same isolation domain. So it's OK to simply drop the global-actor
if we prevent the value from later leaving that isolation domain.
This means we no longer need to warn about code like this:
```
@MainActor func doIt(_ x: [Int], _ f: @MainActor (Int) -> ()) {
x.forEach(f)
// warning: converting function value of type '@MainActor (Int) -> ()' to '(Int) throws -> Void' loses global actor 'MainActor'
}
```
NOTE: this implementation is a bit gross in that the constraint solver
might emit false warnings about casts it introduced that are actually
safe. This is mainly because closure isolation is only fully determined
after constraint solving. See the FIXME's for more details.
resolves rdar://94462333
10 lines
251 B
Swift
10 lines
251 B
Swift
// RUN: %target-typecheck-verify-swift -disable-availability-checking
|
|
|
|
// REQUIRES: concurrency
|
|
// REQUIRES: OS=ios
|
|
|
|
import UIKit
|
|
|
|
@MainActor func issue(stackView: UIStackView) {
|
|
stackView.arrangedSubviews.forEach(stackView.removeArrangedSubview)
|
|
} |