Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README.md: Remove mention of blocking feature now that blocking is non-optional #16

Merged
merged 1 commit into from
Feb 11, 2024
+0 −1
Merged

README.md: Remove mention of blocking feature now that blocking is non-optional #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Loading status checks…
README.md: Remove mention of blocking feature now that blocking is no… 
…n-optional
@joshtriplett
joshtriplett committed Feb 10, 2024

Verified

This commit was signed with the committer’s verified signature.
aduh95 Antoine du Hamel
GPG key ID: 21D900FFDB233756
Verified
Learn about vigilant mode
commit 3b506b7a7cc8d8768c0d19c94bebd9c1fa9cbe4b
1 change: 0 additions & 1 deletion README.md
View file
Original file line number Diff line number Diff line change
@@ -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