AVRO-3841: [Spec] Align the specification of the way to encode NaN to the actual implementations #2463
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.
AVRO-3841
What is the purpose of the change
This PR proposes to slightly change the specification of the way to encode float/double values.
The specification says about the way to encode float/double like as follows.
But the actual implementation in Java uses
floatToRawIntBits
/doubleToRawLongBits
rather thanfloatToIntBits
/doubleToLongBits
.The they are different in the way to encode
NaN
.floatToIntBits
/doubleToLongBits
don't distinguish betweenNaN
and-NaN
butfloatToRawIntBits
/doubleToRawLongBits
do.I confirmed all the implementation distinguish between
NaN
and-NaN
.So, I think it's better to modify the specification.
Verifying this change
All the implementations distinguish between
NaN
and-NaN
.Documentation
This change includes document modification.