Merge "Upgrade rust/crates/num-bigint to 0.4.2" am: ad0d63d6f8 am: 4826407ebf am: d174b394a3

Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/num-bigint/+/1832702

Change-Id: I0c9dc252faf95deb5ccee9060083a09782d7dcf8
tree: 4be250635a1b6a87c88f8294ca079a3289ee2bb6
  1. benches/
  2. out/
  3. patches/
  4. src/
  5. tests/
  6. .cargo_vcs_info.json
  7. .gitignore
  8. Android.bp
  9. build.rs
  10. Cargo.toml
  11. cargo2android.json
  12. LICENSE-APACHE
  13. LICENSE-MIT
  14. METADATA
  15. MODULE_LICENSE_APACHE2
  16. OWNERS
  17. README.md
  18. RELEASES.md
  19. TEST_MAPPING
README.md

num-bigint

crate documentation minimum rustc 1.31 build status

Big integer types for Rust, BigInt and BigUint.

Usage

Add this to your Cargo.toml:

[dependencies]
num-bigint = "0.4"

Features

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.

Random Generation

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.

Releases

Release notes are available in RELEASES.md.

Compatibility

The num-bigint crate is tested for rustc 1.31 and greater.

Alternatives

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.

CrateLicenseMin rustcImplementation
num-bigintMIT/Apache-2.01.31pure rust
rampApache-2.0nightlyrust and inline assembly
rugLGPL-3.0+1.37bundles GMP via gmp-mpfr-sys
rust-gmpMITstable?links to GMP
apintMIT/Apache-2.01.26pure rust (unfinished)

License

Licensed under either of

at your option.

Contribution

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.