commit | ae0206d6d88c13f4bf80b779db03baef13c22360 | [log] [tgz] |
---|---|---|
author | Matthew Maurer <mmaurer@google.com> | Tue May 31 15:54:15 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue May 31 15:54:15 2022 +0000 |
tree | cd1db0c6f34d5e0b137840af7dadf653d717c833 | |
parent | 6be830c65089c73720b3a08d94d149fea2c3eacd [diff] | |
parent | 293ffc6cbbd242c88b203678ae7664cbdb9b95c1 [diff] |
Update TEST_MAPPING am: 293ffc6cbb Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/num-bigint/+/2108465 Change-Id: Id0c611f54baa716332c1ef5782596f838204de62 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.