-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Refactoring] Only unwrap optionals if the handler has an optional error #37235
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
[Refactoring] Only unwrap optionals if the handler has an optional error #37235
Conversation
94de88a
to
d1e3ace
Compare
@swift-ci please test |
This will need to have some changes after Alex's PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
d1e3ace
to
73d8914
Compare
@swift-ci please test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’ve got one small style suggestion.
Also, I think in one test case you are missing a try
. Not sure if the try
is not emitted or if you simply forgot to write it in the CHECK:
line.
Convert to async and add async alternative differ when there is no/an invalid completion handler. In those cases, also check convert to async.
Resolves rdar://73973459
73d8914
to
398124c
Compare
@swift-ci please test |
@hamishknight @ahoppen are you both fine with this one now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢 it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Also added some extra tests for convert to async since it does actually vary from add async slightly.
Resolves rdar://73973459