-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Use OSSALifetimeCompletion in PredictableMemOpt #70477
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
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
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.
Nice!
cc840e2
to
f4bc8d6
Compare
@swift-ci smoke test |
The current algorithm to complete lifetimes is incorrect in a few cases. Use OSSALifetimeCompletion instead. Fixes rdar://119204768
f4bc8d6
to
06f0d15
Compare
@swift-ci smoke test |
@meg-gupta By any chance was this a fix for what looks like some non-deterministic crashes from 5.10? |
@vanvoorden This PR fixed an issue that would have been raised by ownership verification. It looks like your crash is somewhere in the type system. Will be helpful if you can provide a reproducer for the issue you are seeing. |
@meg-gupta Hmm… looks like #71241 and #71730 landed in 6.0… would that look related to what I am seeing in 5.10?
I don't have a clean repro yet… sorry about that. I can keep trying to see if I can find something that crashes consistently in a new package. |
@meg-gupta I think I might have found a repro. #74609. Thanks! |
The current algorithm to complete lifetimes is incorrect in a few cases. Use OSSALifetimeCompletion instead.
Fixes rdar://119204768