-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
fix: Fix one edge case (out of many) of int128 literals not working #20830
Conversation
The test failure doesn't seem to be related to this PR? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #20830 +/- ##
==========================================
+ Coverage 79.63% 79.70% +0.06%
==========================================
Files 1568 1569 +1
Lines 222970 223020 +50
Branches 2544 2546 +2
==========================================
+ Hits 177555 177748 +193
+ Misses 44831 44688 -143
Partials 584 584 ☔ View full report in Codecov by Sentry. |
} | ||
#[cfg(feature = "dtype-i128")] | ||
{ | ||
AnyValue::Int128(v) |
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.
Can we still do a i128::try_from
. Python has unbounded integers.
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 did that initially, and then the compiler pointed out that v
is i128
so the try_from()
always succeeds and is redundant. So at the local scope the current code is the correct thing to do I think?
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.
Ah.. right. 👍
Fixes #20807
See also #20829 for related issues that also seem like they need fixing.