-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Sema][SR-15179] Ignore FunctionArgument inout mismatch if there is already a fix for locator #39257
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
Conversation
Thanks for fixing this! This looks good to me, though I'll let Pavel have the final say. I meant to add this to the original bug report, but there are also a couple of other similar cases that also need fixing, e.g: func tuplify<Ts>(_ fn: (Ts) -> Void) {}
func fn(x: Int..., y: Int...) {}
tuplify(fn)
actor A {}
func isolatedFn(_ x: isolated A, _ y: isolated A) {}
tuplify(isolatedFn) Both calls to If you want to take a look at fixing these too (either in this PR or a follow-up), I can edit the original bug report to include them, or otherwise file a new bug if you want. |
Ah sure, is the same issue so I think we can include them in the same SR and I can adjust in this PR no problem :) |
… is already a fix recorded for function type locator
… is one remove arg fix already for locator
29180ac
to
d53a862
Compare
@swift-ci please smoke test |
@swift-ci Please smoke test |
@swift-ci please smoke test Windows platform |
@swift-ci Please smoke test MacOS platform |
Just ignore the inout fix for individual FunctionArgument if there is a fix already in place.
Resolves: SR-15179
Resolves: rdar://problem/82924296