commit | 121f993ce721caf292d8501dabf3b8ac0ed7206e | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sat Oct 09 05:05:39 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sat Oct 09 05:05:39 2021 +0000 |
tree | 4be250635a1b6a87c88f8294ca079a3289ee2bb6 | |
parent | 138fa7b9296a445c521b0bc06a2a6a6cb5b08476 [diff] | |
parent | b3cb2365b81d4e1aa53d99a4db180572fc288ed7 [diff] |
Snap for 7809064 from b3cb2365b81d4e1aa53d99a4db180572fc288ed7 to tm-release Change-Id: I5082e940cdbe8382de7e32753e0eb0801773cf51
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.