| commit | d352fba4e3a63f1562c70eab571594ed712a9453 | [log] [tgz] |
|---|---|---|
| author | Joel Galenson <jgalenson@google.com> | Mon Aug 30 10:20:45 2021 -0700 |
| committer | Joel Galenson <jgalenson@google.com> | Mon Aug 30 10:20:45 2021 -0700 |
| tree | ad99dc20ef40743400a48c6dbadb8bf16c8e57ff | |
| parent | 0a020ba4a37b8e2dec3da42584dbc0db97e1ddda [diff] |
Update TEST_MAPPING Test: None Change-Id: If641cde341ec8249c9a0225abf066f75132e92ef
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.