-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Add support for opaque result types in structural positions #38392
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
Conversation
This is not ready to merge yet, but considering its size it might be worth doing some code review now. |
fc33fce
to
bced7d6
Compare
45af428
to
7fabab8
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.
I have looked at the type-checker/solver related changes and left a couple of comments inline, overall everything makes sense to me.
abe5600
to
c77d8ba
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.
Constraint system changes look good!
@swift-ci please smoke test |
@swift-ci please smoke test linux |
Currently, we only support opaque result types as top level level types, e.g.
some P
is allowed but not(some P)?
. This branch adds support for opaque result types in structural type positions.