wg-async
may
Our great sponsors
wg-async | may | |
---|---|---|
8 | 17 | |
365 | 1,720 | |
1.6% | - | |
5.9 | 8.2 | |
27 days ago | 4 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
wg-async
- 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.
may
-
Why choose async/await over threads?
https://github.com/Xudong-Huang/may
The project has some serious restrictions and unsound footguns (e.g. around TLS), but otherwise it's usable enough. There are also a number of C/C++ libraries, but I can not comment on those.
-
Asynchronous Clean-Up (in Rust)
> e.g. Linux mutexes
You don't want to use blocking mutexes anyway with async.
> or Rust's Rc
This is only half true. The danger is that two `Rc` that point to the same data are in different threads. But it should be safe to move all of them at once from one thread to another, which is exactly the case if all the `Rc`s involved live inside a `Future`. The problem is that this is a non-local property that's hard to encode in the type system.
> By the way, if you wish to test uncolored async in Rust, you can find an implementation here: https://github.com/Xudong-Huang/may .
FYI that's known to be unsound due to thread locals. And more generally it doesn't seem to give much attention to safety (see for example how it allowed unsound scoped tasks, or the fact it allows doing unsafe operations in some of its macros due to wrong scoping of `unsafe` blocks).
-
What's the Benefit/Allure of Async/Await vs. CSP/Green Threads (and Other Concurrency Models)?
It seems that rust removed native green threads as against it's philosophy: https://stackoverflow.com/questions/29428318/why-did-rust-remove-the-green-threading-model-whats-the-disadvantage#29430403 but there are good CSP libraries e.g. https://github.com/Xudong-Huang/may and yet people really like e.g. Tokio for Async/Await (although it also has greenthreads!) What am I missing?
-
Async Rust Is A Bad Language
Can you admit that you failed in making it a pleasant experience to write async, especially for library authors? I don’t think it’s too late to admit failure and implement something like May https://github.com/Xudong-Huang/may
-
How Much Memory Do You Need to Run 1 Million Concurrent Tasks?
Your benchmark is comparing apples to oranges, you're benchmarking different things. If you wanted to compare a Rust solution to something like what Go does, you would need to use something like this library.
-
Can this new algorithm of Kotlin async be applied to Rust?
Yep. This is the best coroutine library right now https://github.com/Xudong-Huang/may
-
async fn calls can lead to surprising performance problems if they are nested too deeply
I am still intrigued by the stackful coroutine library, May https://github.com/Xudong-Huang/may. I would like to see how far this library can push the boundaries of being a higher level alternative to async
-
Goroutine equivalent
There is also "may" which attempts to be a Rust version of goroutines. I have not used it though, so can't comment on anything further about it.
-
Virtual Threads in Rust?
This library https://github.com/Xudong-Huang/may implement Stackful Coroutines in Rust which I believe is pretty close to what you're asking about. I believe it's a reasonably complete implementation, but it doesn't have much traction because most of the Rust ecosystem is using either async/await or native threads.
-
Working with Strings in Rust
I've never worked with C# so I need to look into that.
The one saving grace with Rust is if everyone decides to say "screw async" and just builds synchronous APIs, then we use something like [May](https://github.com/Xudong-Huang/may) for green threading.
What are some alternatives?
smol - A small and fast async runtime for Rust
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
ideas4 - An Additional 100 Ideas for Computing https://samsquire.github.io/ideas4/
cached - Rust cache structures and easy function memoization
delimited
ocaml - The core OCaml system: compilers, runtime system, base libraries
miniserve - 🌟 For when you really just want to serve some files over HTTP right now!
go - The Go programming language
rlimit - Resource limits
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
monoio - Rust async runtime based on io-uring.
Puma - A Ruby/Rack web server built for parallelism