From 3b506b7a7cc8d8768c0d19c94bebd9c1fa9cbe4b Mon Sep 17 00:00:00 2001 From: Josh Triplett Date: Sat, 10 Feb 2024 14:25:52 -0800 Subject: [PATCH] README.md: Remove mention of blocking feature now that blocking is non-optional --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index a1e210a..9418bd8 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,6 @@ A global executor built on top of async-executor and async-io * `async-io`: if enabled, `async-global-executor` will use `async_io::block_on` instead of `futures_lite::future::block_on` internally. this is preferred if your application also uses `async-io`. -* `blocking`: enable the use of the `blocking` crate through `async_global_executor::spawn_blocking`. * `tokio`: if enabled, `async-global-executor` will ensure that all tasks that you will spawn run in the context of a tokio 1.0 runtime, spawning a new one if required. * `tokio03`: if enabled, `async-global-executor` will ensure that all tasks that you will spawn run in the context of a