commit | ce2228777ebc45916749d49bce8cf28a5aba21a1 | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Sat Oct 09 02:47:01 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Sat Oct 09 02:47:01 2021 +0000 |
tree | 5bf328ca6dfa2265bb0607073a7d26d6cb71e932 | |
parent | de865518a3f1608a752171d9ea973188e397dfae [diff] | |
parent | 9c1e81ef92e5b1e127aedb0f60c6e19ca7650215 [diff] |
Fix failing test am: 45b2647cce am: d1f68b5825 am: 5b09961b72 am: 9c1e81ef92 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/num-bigint/+/1851037 Change-Id: If1cfd8a0d42529ee8d65d58fe953d457b8b50d22
Big integer types for Rust, BigInt
and BigUint
.
Add this to your Cargo.toml
:
[dependencies] num-bigint = "0.4"
The std
crate feature is enabled by default, and is mandatory before Rust 1.36 and the stabilized alloc
crate. If you depend on num-bigint
with default-features = false
, you must manually enable the std
feature yourself if your compiler is not new enough.
num-bigint
supports the generation of random big integers when the rand
feature is enabled. To enable it include rand as
rand = "0.8" num-bigint = { version = "0.4", features = ["rand"] }
Note that you must use the version of rand
that num-bigint
is compatible with: 0.8
.
Release notes are available in RELEASES.md.
The num-bigint
crate is tested for rustc 1.31 and greater.
While num-bigint
strives for good performance in pure Rust code, other crates may offer better performance with different trade-offs. The following table offers a brief comparison to a few alternatives.
Crate | License | Min rustc | Implementation |
---|---|---|---|
num-bigint | MIT/Apache-2.0 | 1.31 | pure rust |
ramp | Apache-2.0 | nightly | rust and inline assembly |
rug | LGPL-3.0+ | 1.37 | bundles GMP via gmp-mpfr-sys |
rust-gmp | MIT | stable? | links to GMP |
apint | MIT/Apache-2.0 | 1.26 | pure rust (unfinished) |
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.