Partially migrate to num-bigint 0.5 - #1499
Merged
Merged
Conversation
tgeoghegan
approved these changes
Sep 2, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Following #1489, this replaces most of our uses of num-bigint 0.4 with num-bigint 0.5. We still need to keep num-bigint 0.4 around in order to work with num-rational 0.4, specifically for conversions to and from floating point types. This PR introduces some private conversion functions where needed for that. In the future, we can update num-rational and eliminate these conversion functions, but this lets us advance the num-bigint version we expose through our public API as far as we can now, ahead of our pre-RFC release.
Supersedes #1471.