-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Serialization] Drop support for serializing LValueType. #9080
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
@swift-ci Please test |
Build failed |
@swift-ci Please test macOS |
Build failed |
@swift-ci Please test macOS |
Build failed |
case decls_block::INOUT_TYPE: { | ||
TypeID objectTypeID; | ||
decls_block::LValueTypeLayout::readRecord(scratch, objectTypeID); | ||
decls_block::InOutTypeLayout::readRecord(scratch, objectTypeID); |
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.
Before, we were serializing INOUT_TYPE using LValueTypeLayout. Is this what's causing the test failure here?
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.
Nope, the test failure is completely unrelated. There's unfortunately no static or dynamic type-checking on the layout deserialization, although maybe there should be.
This type never appears in API boundaries or in SIL instructions, which means it never gets serialized.
46d60a2
to
f7edba3
Compare
@swift-ci Please test macOS |
@swift-ci Please smoke test Linux |
Build failed |
This type never appears in API boundaries or in SIL instructions, which means it never gets serialized.