| commit | f58951b04cecc3cb7f4be0e89530a00e9a49c257 | [log] [tgz] |
|---|---|---|
| author | Joel Galenson <[email protected]> | Wed Dec 15 18:07:05 2021 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed Dec 15 18:07:05 2021 +0000 |
| tree | 0545506bd7f7032e563d2653d92f3e19204249cd | |
| parent | 508e41fddb37d9980d4872956c2d0794ac16cd03 [diff] | |
| parent | e09350bf19fb375aac3549bc68765150dd8ecbda [diff] |
Merge "Refresh Android.bp, cargo2android.json, TEST_MAPPING." am: c020b9e655 am: 521c36ac99 am: 2b07189547 am: e09350bf19 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/num-bigint/+/1912502 Change-Id: Id72c660c9bbc8e16a17631b33c6bc7a3050ba5b6
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.