Treat big ints as floats via feature flag "big-int-as-float" #363
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.
Currently simd-json errors when a to large integer overflows while parsing.
This PR adds a feature flag
big-int-as-float
that handles cases when int overflows and interprets that as a float instead.The downside is that you loose some precision but that's ok if you opt into it and how it currently works in most JavaScript based engines.
For example:
JSON.parse("999999999999999999999999999999")
in Chrome (v8) returns 1e+30