This repository has been archived by the owner on Mar 23, 2021. It is now read-only.
Deduplicate serialization efforts without locking in one a specific one #2911
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
thomaseizinger
force-pushed
the
remove-serialization-duplication
branch
from
2823807
to
aea002a
Compare
rishflab
approved these changes
Jul 1, 2020
thomaseizinger
force-pushed
the
remove-serialization-duplication
branch
from
aea002a
to
645b5e1
Compare
tcharding
approved these changes
Jul 1, 2020
thomaseizinger
force-pushed
the
remove-serialization-duplication
branch
from
645b5e1
to
4cc2288
Compare
This patch is meant to set an example on how to effectively deal with the need for repeated serialization needs without locking a type into one a specific one.
|
bors r+ |
|
Build succeeded: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 patch is meant to set an example on how to effectively deal with the need for repeated serialization needs without locking a type into one a specific one.
In addition, this allows users of the
comitlibrary to reuse these serialization strategies.