rlimit
Resource limits (by Nugine)
wg-async
Working group dedicated to improving the foundations of Async I/O in Rust (by rust-lang)
| rlimit | wg-async | |
|---|---|---|
| 1 | 8 | |
| 31 | 365 | |
| - | 1.1% | |
| 5.9 | 5.9 | |
| about 1 month ago | about 1 month ago | |
| Rust | Rust | |
| MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rlimit
Posts with mentions or reviews of rlimit.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-10-29.
wg-async
Posts with mentions or reviews of wg-async.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-08.
- Async Rust Is A Bad Language
-
Catch 22! Rust in Review
I believe the solution mentioned in rust-lang/wg-async is the way to go: Add traits like AsyncWrite, AsyncRead, Executor/Runtime to the std so that tokio/async-std can implement them.
-
Async Rust: What is a runtime? Here is how tokio works under the hood
This is a consequence of runtimes relying on global variables that their core future types are dependent on. Creating abstractions to solve this problem is one of the main goals of the the async working group [0].
[0]: https://github.com/rust-lang/wg-async
-
How should I structure an async/await/futures program with multiple event sources and mutable state?
Provided the futures you're selecting over are cancellation safe the plain loop over select! should be fine. Multiple channels in particular are safe to select over - if you have futures that aren't cancellation safe, you can just wrap them up in a task on the end of a channel and then select on that.
- Monoio – A thread-per-core Rust async runtime with io_uring
-
What Rust feature are you waiting for?
I'd like to be able to write runtime agnostic async libs.
-
Rust Weird Expressions
You might be interested in taking a look at and potentially participating in the "Async Vision Document"[1] which is an exercise the team is going through to collect feedback about the current state of the ecosystem and what the pain points are, as well as a way to lay doing what the desired future state of async Rust should be[2]. The process is happening, as you would expect, in the open and there's still time to influence it[3] if your concerns aren't yet addressed or even mentioned[4].
[1]: https://rust-lang.github.io/wg-async-foundations/vision.html
[2]: https://blog.rust-lang.org/2021/03/18/async-vision-doc.html
[3]: https://github.com/rust-lang/wg-async-foundations/pulls
[4]: https://github.com/rust-lang/wg-async-foundations/issues
-
Building a shared vision for Async Rust
Thanks for the feedback. I posted this comment to a relevant github issue, fyi.
What are some alternatives?
When comparing rlimit and wg-async you can also consider the following projects:
rust - Empowering everyone to build reliable and efficient software.
smol - A small and fast async runtime for Rust