-
Notifications
You must be signed in to change notification settings - Fork 1k
Implement full-range i256::to_f64
to eliminate ±∞ saturation for Decimal256 → Float64 casts
#7986
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6842524
feat: implement to_f64 method for i256 to convert to f64 representation
kosiew 40a65bf
feat: enhance decimal256_to_f64 function for improved conversion and …
kosiew a426bcc
Update arrow-cast/src/cast/mod.rs
kosiew 049c2e6
refactor: replace decimal256_to_f64 fn with i256::to_f64 method and m…
kosiew File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking this through:
high
is zero (no significant bits), then conversion to f64 is exact (tho useless)low
, converted to f64high
has1..=53
significant bits, then conversion to f64 is exact (no rounding)low
(already converted to f64) will round as neededhigh
has54..
significant bits, then conversion to f64 will use the 54th bit to roundlow
takes, because it's so small that adding it doesn't change the answerA bit expensive, but I think it covers all the cases with no weird rounding effects?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect we could do better by manually twiddling bits, but that's probably a good follow-up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bit twiddling that I think would work:
i256::leading_zeros()
that follows the semantics of all the otherleading_zeros
for integral typesThe above should work for both positive and negative values
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tracking in
i256
tof64
#8013