New format #15
Merged
New format #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new binary format and backing implementation for the next major release.
The code is less complex, and contains fewer edge cases.
The new format is a bit less efficient in some cases, but supports all features of the codable protocol, including providing the number of elements in unkeyed containers.
The new format also fixes the compatibility with SIMD types (#14).
The new binary format is detailed in the
BinaryFormat.mddocument.Migration options from the previous format are stated in the readme, including a new readme to import a swift package that can decode the old format.