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.
This fixes #2772 and a few of other issues I found:
rnd_i
would first convert big floats into an i64, before converting them into anIBig
round/1
would add0.5
to big integers, losing precision beyond±2 ^ 53
gcd/2
would attempt to cast its second argument to anisize
before computing the gcd usingIBig::gcd
, triggering apanic!()
min/2
andmax/2
would return the float version of their arguments if their types didn't matchThis PR is accompanied by a test suite (that @UWN might be interested in) for the behavior of
is/2
, both after being compiled and being metacalled. Implementation-specific behavior (like bitshifting negative numbers) is excluded from this test suite.I ran the integration tests with
cargo-tarpaulin
to get a report and help me find uncovered edge cases. I chose not to test special cases likepow(integer, integer)
, since it's unclear to me whether or not smallNumber::Integer
should be returned from computations (likeX is 2 ^ 64 - 2 ^ 64
).Each of these changes (including the addition of the new test suite) were placed in their own commits.