commit | 9e8f82cf2c86e4c9f9fd3bf12f372184d8104214 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Thu Jun 03 03:05:35 2021 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Thu Jun 03 03:05:35 2021 +0000 |
tree | 94d4ebfabd135e1221ef63e678539ffb5acb6c19 | |
parent | 7c89cddc53280cfa14fa517c37891faebdee399b [diff] | |
parent | 5b314a6474a13d54bef0791ccaa63b3860eb4ec9 [diff] |
Snap for 7418644 from 5b314a6474a13d54bef0791ccaa63b3860eb4ec9 to tm-release Change-Id: Ibe71e3f0718ac345ffc05bad2ff047942f9b058c
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.