-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[TypeChecker] Do not attempt to skip typechecking for didSet #34569
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
[TypeChecker] Do not attempt to skip typechecking for didSet #34569
Conversation
5a6299b
to
12683c1
Compare
@swift-ci please 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.
Thanks!
@swift-ci please test Windows platform |
Build failed |
@swift-ci please test OS X platform |
15f8eb4 (see PR#26632) introduced refined didSet semantics where the `oldValue` parameter is skipped if it isn't used. This would perform typechecking, but later try to set the body to skipped and thus fire an assert. For now, do not attempt to skip typechecking of didSet accessors. Still skip outputting their SIL though.
12683c1
to
ea365d5
Compare
I fixed up the test so that it does the correct CHECK-NOT now :). |
@swift-ci please smoke test |
⛵ |
15f8eb4 (see PR#26632) introduced
refined didSet semantics where the
oldValue
parameter is skipped if itisn't used. This would perform typechecking, but later try to set the
body to skipped and thus fire an assert.
For now, do not attempt to skip typechecking of didSet accessors. Still
skip outputting their SIL though.