Enable unwrap_newtypes extension during serialization#333
Merged
Conversation
Member
Author
|
@torkleyy This PR is quite minimal and just mirrors the deserialization implementation. A follow-up for |
Member
Author
|
@torkleyy Does this PR look good to you? |
1 task
torkleyy
added a commit
to torkleyy/ron
that referenced
this pull request
Jun 6, 2022
Enable `unwrap_newtypes` extension during serialization
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.
This PR fixes #284 and implements newtype unwrapping during serialization. E.g.
now serializes to
4.2instead ofMyFloat(4.2)or(4.2). Enabling the extension also adds the extension enabling attribute to the top of the serialized RON.CHANGELOG.md