Clarify: serialization formats#437
Merged
Merged
Conversation
Factors out a section on Map ordering which was duplicated between the previous two subsections. Also clarifies that a different serialization format may use whichever natively supported primitives it likes. Closes #337
leebyron
force-pushed
the
serialization-clarify
branch
from
May 1, 2018 02:40
0c37a3e to
18bc75a
Compare
This file contains hidden or 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
2 participants
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.
Factors out a section on Map ordering which was duplicated between the previous two subsections.
Also clarifies that a different serialization format may use whichever natively supported primitives it likes.
Closes #337