Google Git
Sign in
android/platform/external/rust/crates/rayon-core/1dbe5a8cfae0bf1786f5832dffbbe229b8e4d10e
commit
1dbe5a8cfae0bf1786f5832dffbbe229b8e4d10e
[log]
author
Joel Galenson <[email protected]>
Mon Aug 30 21:30:09 2021 +0000
committer
Automerger Merge Worker <[email protected]>
Mon Aug 30 21:30:09 2021 +0000
tree
ad99dc20ef40743400a48c6dbadb8bf16c8e57ff
parent
f14cfd80ef571a5fbfe751cf670a6c424f72fc2f [diff]
parent
da314a0aa78dfe303761e25016db5266a040b51f [diff]
Update TEST_MAPPING am: d352fba4e3 am: dc1fefbea0 am: da314a0aa7

Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1813860

Change-Id: Iada09afbe0652460dde29dd6cc9cce5ccce053bd
tree: ad99dc20ef40743400a48c6dbadb8bf16c8e57ff
  1. src/
  2. tests/
  3. LICENSE ⇨ LICENSE-APACHE
  4. .cargo_vcs_info.json
  5. Android.bp
  6. build.rs
  7. Cargo.toml
  8. Cargo.toml.orig
  9. LICENSE-APACHE
  10. LICENSE-MIT
  11. METADATA
  12. MODULE_LICENSE_APACHE2
  13. OWNERS
  14. README.md
  15. TEST_MAPPING
README.md

Rayon-core represents the “core, stable” APIs of Rayon: join, scope, and so forth, as well as the ability to create custom thread-pools with ThreadPool.

Maybe worth mentioning: users are not necessarily intended to directly access rayon-core; all its APIs are mirror in the rayon crate. To that end, the examples in the docs use rayon::join and so forth rather than rayon_core::join.

rayon-core aims to never, or almost never, have a breaking change to its API, because each revision of rayon-core also houses the global thread-pool (and hence if you have two simultaneous versions of rayon-core, you have two thread-pools).

Please see Rayon Docs for details about using Rayon.

Rayon-core currently requires rustc 1.36.0 or greater.