[5.5][Async Refactoring] Split ambiguous (error + success) completion handler calls into success and error case #38307
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.
Optional
, this could cause us to generate code that didn't compile, because wethrow
ed theError?
or passed it tocontinuation.resume(throwing)
, both of which didn't work.We now generate an
if let
statement that checks if the error isnil
. If it is, the error is thrown. Otherwise, we interpret the call as a success call and return the result.completion(result, error)
instead ofcompletion(result, nil)
)Example 1 (convert to continuation)
Base Code
Old Refactoring Result
New Refactoring Result
Example 2 (convert to async/await)
Base Code
Old Refactoring Result
New Refactoring Result