feat: Support serde_json's arbitrary_precision feature #102
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
jpmckinney
force-pushed
the
arbitrary_precision
branch
from
0b81c56 to
e5b3249
Compare
jpmckinney
force-pushed
the
arbitrary_precision
branch
from
e5b3249 to
ed9f9f8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
closes #101
I'm not sure of your preferences with respect to errors and tests. I think the errors are unreachable unless a user specially crafts JSON that uses
$serde_json::private::Number(which is an issue that has been reported to serde-json).Edit: I force-pushed a new commit. Original commit would convert large JSON integers to floats.