aboutsummaryrefslogtreecommitdiff
path: root/vendor/rayon-core/README.md
diff options
context:
space:
mode:
authorValentin Popov <valentin@popov.link>2024-07-19 15:37:58 +0300
committerValentin Popov <valentin@popov.link>2024-07-19 15:37:58 +0300
commita990de90fe41456a23e58bd087d2f107d321f3a1 (patch)
tree15afc392522a9e85dc3332235e311b7d39352ea9 /vendor/rayon-core/README.md
parent3d48cd3f81164bbfc1a755dc1d4a9a02f98c8ddd (diff)
downloadfparkan-a990de90fe41456a23e58bd087d2f107d321f3a1.tar.xz
fparkan-a990de90fe41456a23e58bd087d2f107d321f3a1.zip
Deleted vendor folder
Diffstat (limited to 'vendor/rayon-core/README.md')
-rw-r--r--vendor/rayon-core/README.md11
1 files changed, 0 insertions, 11 deletions
diff --git a/vendor/rayon-core/README.md b/vendor/rayon-core/README.md
deleted file mode 100644
index 6e2ebe2..0000000
--- a/vendor/rayon-core/README.md
+++ /dev/null
@@ -1,11 +0,0 @@
-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 Docs]: https://docs.rs/rayon/
-
-Rayon-core currently requires `rustc 1.63.0` or greater.