Feature/encode struct names : using boost.type index to disambiguate variants instead of fields collection#2
Merged
daminetreg merged 3 commits intomasterfrom Dec 18, 2015
Conversation
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
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.
Hi @linkineo,
Could you help me reviewing this ?
It is in regards of disambiguating variants with the struct name.
This ends up in such json when a member struct is in a variant, this however drops variant disambiguation for std::string vs double vs int, because I don't disambiguate anymore for them.
Additionally it has the advantage that I don't rely on trying the deserialization process to ensure it is the right type.