Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve JsonNodeDeserializer handling of NaN wrt USE_BIG_DECIMAL_FOR_FLOATS #4245

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

cowtowncoder
Copy link
Member

Based on improved JsonParser.isNaN() which now only reports explicit NaN and not possible value over-/underflow (for double and float)

@cowtowncoder
Copy link
Member Author

/cc @pjfanning @JooHyukKim

I think this is safe now; not 100% sure if this:

FasterXML/jackson-core#1149

is needed; possibly is to avoid possible extra work and/or accuracy loss due to existing getNumberType() for JSON coercing value into Double.

But first things first, I think this is still an improvement.

@cowtowncoder cowtowncoder merged commit 26f232a into 2.17 Dec 8, 2023
5 checks passed
@cowtowncoder cowtowncoder deleted the tatu/2.17/json-node-bigdecimal-nan-coercion branch December 8, 2023 00:10
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.

2 participants