Skip to content

feat: Support serde_json's arbitrary_precision feature#102

Open
jpmckinney wants to merge 1 commit intodavidhewitt:mainfrom
jpmckinney:arbitrary_precision
Open

feat: Support serde_json's arbitrary_precision feature#102
jpmckinney wants to merge 1 commit intodavidhewitt:mainfrom
jpmckinney:arbitrary_precision

Conversation

@jpmckinney
Copy link

@jpmckinney jpmckinney commented Nov 26, 2025

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.

Copy link
Owner

@davidhewitt davidhewitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this, and sorry for the very slow review.

Seems like this is the right approach to handle this case. Ouch.

Can you please add:

  • CHANGELOG entry
  • Note of this feature in the README (maybe in a new # Features section)
  • Adjust CI to run both with and without this feature enabled

... and then let's get this merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for serde-json arbitrary_precision

2 participants