Skip to content

Conversation

@DougGregor
Copy link
Member

To improve forward compatibility, ignore any unknown records encountered during deserialization rather than throwing an error. libclang has behaved this way forever, and we should do the same.

To improve forward compatibility, ignore any unknown records
encountered during deserialization rather than throwing an error.
libclang has behaved this way forever, and we should do the same.
@DougGregor
Copy link
Member Author

@swift-ci please smoke test

@DougGregor
Copy link
Member Author

@swift-ci please test

Copy link
Member

@compnerd compnerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DougGregor where is this used? IIRC swift-driver has a copy of the Bitcode deserialization logic.

@DougGregor
Copy link
Member Author

@DougGregor where is this used? IIRC swift-driver has a copy of the Bitcode deserialization logic.

SwiftPM has a little-used client of this (swift package diagnose-api-breaking-changes). swift-driver uses this version in some of its tests

@DougGregor DougGregor merged commit 1ed3a9b into main Jan 6, 2023
@DougGregor DougGregor deleted the serialized-diags-ignore-unknown-records branch January 6, 2023 21:06
DougGregor added a commit that referenced this pull request Jan 6, 2023
To improve forward compatibility, ignore any unknown records
encountered during deserialization rather than throwing an error.
libclang has behaved this way forever, and we should do the same.

(cherry picked from commit 1ed3a9b)
DougGregor added a commit that referenced this pull request Jan 7, 2023
To improve forward compatibility, ignore any unknown records
encountered during deserialization rather than throwing an error.
libclang has behaved this way forever, and we should do the same.

(cherry picked from commit 1ed3a9b)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants