From 549616ca6812757856758b07cc4a2a28362b667d Mon Sep 17 00:00:00 2001 From: Pop Date: Thu, 20 Jun 2024 10:40:32 +0900 Subject: [PATCH] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b67a4b05..7e727d93 100644 --- a/README.md +++ b/README.md @@ -13,13 +13,13 @@ This crate is inspired by [monoio](https://github.com/bytedance/monoio/). ## Why not Tokio? -Tokio is a great generic-propose async runtime. +Tokio is a great generic-purpose async runtime. However, it is poll-based, and even uses [undocumented APIs](https://notgull.net/device-afd/) on Windows. We would like some new high-level APIs to perform IOCP/io_uring. Unlike `tokio-uring`, this runtime isn't Tokio-based. This is mainly because that no public APIs to control IOCP in `mio`, -and `tokio` won't public APIs to control `mio` before `mio` reaches 1.0. +and `tokio` won't expose APIs to control `mio` before `mio` reaches 1.0. ## Why not monoio/tokio-uring/glommio? @@ -30,7 +30,7 @@ They don't support Windows. Add `compio` as dependency: ``` -compio = { version = "0.10.0", features = ["macros"] } +compio = { version = "0.11.0", features = ["macros"] } ``` Then we can use high level APIs to perform filesystem & net IO.