-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Placeholder types: take two #36740
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
Placeholder types: take two #36740
Conversation
This comment has been minimized.
This comment has been minimized.
0464850
to
1ea1cf7
Compare
@Jumhyn This is in my queue, going to try to look asap. |
5e0c19d
to
11ac05d
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.
LGTM! I have left some comments inline, but they are mostly minor. I also think it might be worth it to land some part of this PR separately.
9901570
to
8e5519e
Compare
5403358
to
0c614e3
Compare
@xedin So it seems like things mostly work out just fine. The only additional failure is in
Note: we get the diagnostic twice because the parameter and result type both require that |
@Jumhyn Sorry it took me a bit to respond, I'm on vacation this week. I think new diagnostics make sense, they are definitely better than ambiguities especially considering that other overload is invalid, so I'd say we should proceed with failing in type resolution + failing on |
0c614e3
to
b7a0556
Compare
No worries at all @xedin, hope you're having a nice vacation! Please feel free to ignore me until you're back. :) For whenever you're back: yes, I agree the diagnostics are improved! Just wanted to make sure I wasn't missing anything. I've rebased to fold the type resolution failure into these changes, so I believe all your comments should be addressed at this point. |
b7a0556
to
6b95569
Compare
Hey @xedin, if you're still on vacation then disregard, just wanted to put this back on your radar in case it slipped off while you were out! |
I'm back and it did slip from my radar unfortunately but now it's back in the fold :) |
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!
@xedin Alright, updated with |
Is the [DNM] marker in this title still relevant? Any changes you still want to make before I merge this? |
@jckarter No, assuming that all tests are still passing (🤞) there aren't any changes I intend to make here. Should be merge-ready! |
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. Just a couple of nitpicks
Courtesy of @exfalsoquodlibet on the forums
a7d76ff
to
c1ed499
Compare
Thanks @rintaro, your comments have been addressed! |
@swift-ci please test |
@swift-ci please test |
@xedin Good to merge? |
🎉 @Jumhyn Could you update CHANGELOG.md too? |
Implements the placeholder types proposal.