commit | 05b9c6f1d30db73fcc6d1ea9efdfdb41c27bbc5b | [log] [tgz] |
---|---|---|
author | Josh Wu <joshwu@google.com> | Fri Jul 29 06:00:45 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jul 29 06:00:45 2022 +0000 |
tree | ca7dae8bc271b10c7ceae1479e7639abf1df5a2a | |
parent | bc72cc1ad9f57d86c75fda0158d1037168847455 [diff] | |
parent | 33614408ab2ef5fe178abf33906be9545cc852cb [diff] |
Make crate vendor available am: 33614408ab Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/num-bigint/+/2167185 Change-Id: I843fcaeba94f96d33e0f0a08f21dbdf4b1249673 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.