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
[SR-5688] [Sema] Handle key path component base type on MemberAccessOnOptionalBaseFailure #32376
[SR-5688] [Sema] Handle key path component base type on MemberAccessOnOptionalBaseFailure #32376
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.
Thanks for the fix!
136733c
to
fa11612
Compare
@hamishknight @xedin There are still some tests failing I have to look, so I'll ping you when this is ready for a review :) |
Right, this is ready :) @hamishknight @xedin |
5c5f63d
to
4e3f54d
Compare
…e to handle key path component member base types
…n correct location
…ure to emit the correct diagnostics and fixes
… cases with respective diagnostics
…ber is a key path component.
…ostics as per suggestion
d60f4f7
to
316abfc
Compare
@hamishknight Thank you for the review |
Right, now tests are happy so this is ready for review :) |
c90927b
to
74f7651
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! Just a couple more comments
a2d1817
to
8fe2a61
Compare
624c9a9
to
8fd3f02
Compare
…tion return types when possible on simplifyOptionalObjectConstraint
8fd3f02
to
7f57de4
Compare
…oot infered as optional types
…ttempt InsertCall fix before remove unwrap
c2060c6
to
3a961c8
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.
Thanks again! I'll let @xedin have the final say, but this looks good to me!
Please make sure to do a squash-and-merge when merging to ensure the git history is kept clean (congrats on commit access btw!).
Sure, Thank you for the review @hamishknight :) I've learned some nice new things here \o/ |
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 left a minor comment otherwise LGTM!
…OptionalBaseFailure construction
@swift-ci please smoke test |
@xedin The windows build didn't trigger or it just didn't show on the github UI like that one in the other PR? |
Looks like it just didn't report the status - https://ci-external.swift.org/view/Pull%20Request/job/swift-PR-windows/4504/ |
@swift-ci please smoke test Windows platform |
Squashed and merged, Thank you @hamishknight @xedin :) |
The fix was being recorded but it was failing to handle the key path component type.
This just handles the
KeyPathComponent
locator.Resolves SR-5688.