commit | 406c1dd659b5e6876fe7cf78795e2071f37b9e7a | [log] [tgz] |
---|---|---|
author | James Farrell <jamesfarrell@google.com> | Tue May 21 19:01:28 2024 +0000 |
committer | James Farrell <jamesfarrell@google.com> | Tue May 21 19:01:28 2024 +0000 |
tree | 667865e857db3a0b8a6fbd3b8d0c653fe32072fc | |
parent | 682771a8de10e8857e4ae071b7799072ddf88a8e [diff] |
Update Android.bp by running cargo_embargo Test: ran cargo_embargo Change-Id: I5f8d3777d045070b6853c19e9549d082acf18511
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.63.0
or greater.