Json floats #53
Merged
Json floats #53
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 really does not jive well with our mental model of tokens which are agnostic to particular serial format. And the idea of potentially *silently* losing precision of a number when processed in this way seems rather alarming to me, even if it is considered (to some extent?) "normal" for json to do so.
This was referenced Dec 11, 2020
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.
Some fixes to JSON floats, which had previously been nearly unsupported by this library.
Parsing JSON will no longer parse really large numbers (e.g., >64bit) as floats unless they have some clear indication of not being an integer (decimal point, exponent, etc).
Emitting floats is actually supported. Previously this panicked.