| commit | 28115b62ceed05f762f7b163c640c08f3c294427 | [log] [tgz] |
|---|---|---|
| author | Jakub Kotur <qtr@google.com> | Tue Mar 16 20:22:32 2021 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Mar 16 20:22:32 2021 +0000 |
| tree | f3b875c61b673490a50fc6a7e3a578c27e9c78c6 | |
| parent | cc6ff67f9992c7f991228396a897677a0def9a78 [diff] | |
| parent | 7c5f66a679b75a8325d0775df538492947a1bd0d [diff] |
Initial import of rayon-core-1.9.0. am: 3b7f317415 am: 52de626812 am: 7c5f66a679 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1621088 Change-Id: I50d4474c5dba459e0dbfc7678a911847b0029504
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.