-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[silgen] Require ManagedValue::{forward,assign}Into to only accept pl… #14566
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
[silgen] Require ManagedValue::{forward,assign}Into to only accept pl… #14566
Conversation
@swift-ci test |
@swift-ci test source compatibility |
Build failed |
@swift-ci test os x platform |
Build failed |
eab7304
to
7b0204a
Compare
@swift-ci test |
@swift-ci source compatibility |
@swift-ci test source compatibility |
I am going to land the 3 sub patches in separate PRs and then commit only the last commit in this PR. It passed the source compat suite, so we should be ok. |
…usOne ManagedValues. We already have this requirement on RValues, so it is natural to extend it to ManagedValue. The main reason why I am doing this though is to tighten up SILGen asserts to help me catch places where we forward +0 arguments into memory without a copy/cleanup. rdar://34222540
7b0204a
to
713e5f9
Compare
@swift-ci test |
1 similar comment
@swift-ci test |
@swift-ci test source compatibility |
Build failed |
@swift-ci test source compatibility |
1 word to say: WOOT! |
…usOne ManagedValues.
We already have this requirement on RValues.
This also lets me clean up a little bit of code in RValue as well.