| commit | bb757ea78f53bca2b8d08781a038059b610da331 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Fri Nov 04 07:25:44 2022 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Fri Nov 04 07:25:44 2022 +0000 |
| tree | 8efd4931d7f25714ad4b5334427658b52568dd9f | |
| parent | 4ec41dcfd2fba71c87edbe800c50f0680ca2a523 [diff] | |
| parent | 3e3a2de747abc46c4364490e30b17cbe0f94e4be [diff] |
Snap for 9255242 from 3e3a2de747abc46c4364490e30b17cbe0f94e4be to mainline-networking-release Change-Id: I3ccfcf9a3a77a9f9e677c39413b3ccd73f0e1899
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.