#126 Generalize serialization/deserialization features #134
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
fktn-k
added
the
improvement
fktn-k
deleted the
feature/126_generalize_serialization_deserialization
branch
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.
To generalize serialization/deserialization features of YAML nodes, those features are wrapped as basic_node class APIs: deserialize() & serialize().
Internal operations are still executed by basic_serializer/basic_deserializer class objects which have been moved to detail directory/namespace.
This will enable us to improve internal operations in serialization/deserialization features while keeping backward compatibility of those APIs.