[Migrator] Migrate references to shorthand closure params (e.g. $0, $1) where affected by SE110 #9711
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Swift 3:
$1
or above type checked against a function type that takes a single tuple argument with that arity$0
(or$0.1
etc) type checked against a function type that takes multiple argumentsbut neither compiles in Swift 4. This patch migrates shorthand references for:
$1
to$0.1
0.
if one exists or substituting a tuple of the correct arity if it doesn't, e.g.$0.1
to$1
and$0
to($0, $1, $2)
Resolves rdar://problem/31969538