You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may or may not be difficult with the dom parser.
Future simdjson C releases may make this easier but this functionality might not be planned for arbitrary-precision integers (only floats) - https://github.com/simdjson/simdjson/pull/1886 is in review pending manual tests and performance testing.
See my PR comment for a note on how BIGINT might be possible in followup
https://github.com/simdjson/simdjson/issues/167 suggests it's possible with the ondemand parser, but that may be slightly slower than the dom parser?
https://github.com/simdjson/simdjson/issues/425#issuecomment-883605600 mentions this is supported in the ondemand api
We may want to take the tiny performance hit just to imitate php's behavior for numbers in json_decode()
Note that this is effectively supported now with the On Demand API and documented as such:
This may or may not be difficult with the dom parser.
Future simdjson C releases may make this easier but this functionality might not be planned for arbitrary-precision integers (only floats) -
https://github.com/simdjson/simdjson/pull/1886
is in review pending manual tests and performance testing.https://github.com/simdjson/simdjson/issues/167
suggests it's possible with the ondemand parser, but that may be slightly slower than the dom parser?https://github.com/simdjson/simdjson/issues/425#issuecomment-883605600
mentions this is supported in the ondemand apiWe may want to take the tiny performance hit just to imitate php's behavior for numbers in json_decode()
The text was updated successfully, but these errors were encountered: