-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CSApply] Handle OptionalForce component when is initial component on key path expr #33623
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] Handle OptionalForce component when is initial component on key path expr #33623
Conversation
fd64729
to
5fc9008
Compare
2f310f4
to
2c65ee5
Compare
@swift-ci Please smoke test |
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.
One more minor comment, but this looks good to me!
2c65ee5
to
7815ecf
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!
@swift-ci Please smoke test |
Something wrong with the build? It still not triggered 🤔 |
Looks like it didn't get triggered. This can sometimes happen after a force-push, usually waiting a little bit and re-trying fixes it. @swift-ci please smoke test |
Thanks @hamishknight @xedin :) |
Fixing crash when ForceOptional kind is the first component on CSApply.
Resolves SR-13442.