-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CSApply] Fixed type-checked subexpression output bug for multi-state… #59260
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
[CSApply] Fixed type-checked subexpression output bug for multi-state… #59260
Conversation
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! Note that there is a slight semantic difference here as well - rewriteTarget
is called for each syntactic element in the body but applySolution
is called only once which means that processing is going to be more incremental in this case too.
@swift-ci please test |
@swift-ci please test source compatibility |
@amritpan Linux failures are what I was afraid of - looks putting |
6dbaaa9
to
3ad8638
Compare
3ad8638
to
9a0978a
Compare
6dbaaa9
to
3a38d7a
Compare
380ff81
to
38d6ea8
Compare
…e-checked to show their application solution status, as applicable for tap expressions and multi-statement closures.
38d6ea8
to
d7266d6
Compare
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, thank you!
@swift-ci please test |
…ment closures
Previously the type-checked subexpressions of a multi-statement closure were being printed with only partial bindings. This fix ensures that subexpressions are printed with all of their type-checked bindings.