-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CS] Some more NFC changes #64149
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
[CS] Some more NFC changes #64149
Conversation
66307d8
to
8c8259c
Compare
Some clients such as code completion ought to be able to reference this without pulling in the entirety of ConstraintSystem.h.
Fill in some nodes that previously weren't being walked, and bail with `None` if the walk is terminated, rather than filling the resulting SolutionApplicationTarget with null pointers. This method currently isn't called anywhere, but I'm planning on using it shortly, so this is an NFC change for now.
8c8259c
to
2976edb
Compare
@swift-ci please test |
@hamishknight Why is |
Mostly consistency, we have SyntacticElement{ConstraintGenerator, SolutionApplication} and it makes sense to move away from "solution application" because it's a solver target as well. |
I still find |
No, it's not only for closures, it could be used in any supported context which includes function/accessor declarations and if/switch expressions and soon string interpolations. I personally don't like |
Maybe |
I suggested |
Totally works for me as well. There is no |
Split a couple more changes off #63963