Customizable buffer type by Deserializer #1354
Closed
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
This was referenced Aug 11, 2018
|
Closing because I am no longer actively working on this. It may be better to revisit after associated type defaults are stabilized. rust-lang/rust#29661 |
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.
This change allows Deserializer impls to select some type to be used for temporary buffering of untagged, internally tagged, adjacently tagged, and flattened content. By default Serde will continue to use our own private
Content<'de>buffer type, but for example serde_json could choose to use a serde_json::Value as its buffer to fix #1183.Needs much more work and polish but it looks like this approach can work.