flowmatic
rust-async-examples
| flowmatic | rust-async-examples | |
|---|---|---|
| 2 | 1 | |
| 249 | 0 | |
| - | - | |
| 7.3 | 10.0 | |
| about 1 month ago | over 1 year ago | |
| Go | Rust | |
| MIT License | - |
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.
flowmatic
-
Async rust – are we doing it all wrong?
I do that of course, and that's one of the easiest ways to use async Rust. In real projects you need much more however. F.ex. I had to code an example of how to add tasks to an already running pool of tasks and posted my findings here: https://github.com/dimitarvp/rust-async-examples/blob/main/e... (there's #2 as well with some more comments and a different approach).
The fact that I needed to make a GitHub repo and start making show-and-tell demos on how to do various things with async Rust to me is both a red flag and me being diligent BUT it should be more obvious. And promoted in docs.
Rust started suffering from "you got all the nuts and bolts in place, now build your own solution, son" syndrome which I grew to dislike. Too low-level. I wouldn't mind something akin to e.g. Golang's flowmatic library (check the first two examples at the top of the README): https://github.com/carlmjohnson/flowmatic
- Flowmatic: Structured concurrency made easy
rust-async-examples
-
Async rust – are we doing it all wrong?
I do that of course, and that's one of the easiest ways to use async Rust. In real projects you need much more however. F.ex. I had to code an example of how to add tasks to an already running pool of tasks and posted my findings here: https://github.com/dimitarvp/rust-async-examples/blob/main/e... (there's #2 as well with some more comments and a different approach).
The fact that I needed to make a GitHub repo and start making show-and-tell demos on how to do various things with async Rust to me is both a red flag and me being diligent BUT it should be more obvious. And promoted in docs.
Rust started suffering from "you got all the nuts and bolts in place, now build your own solution, son" syndrome which I grew to dislike. Too low-level. I wouldn't mind something akin to e.g. Golang's flowmatic library (check the first two examples at the top of the README): https://github.com/carlmjohnson/flowmatic
What are some alternatives?
dream-programming-language - notes on my dream programming language
channelify - Make functions return a channel for parallel processing via go routines.
ideas5 - Batch 5 of Ideas for Computing
pool - :speedboat: a limited consumer goroutine or unlimited goroutine pool for easier goroutine handling and cancellation
Rouille, Rust web server middleware - Web framework in Rust
gpool - gpool - a generic context-aware resizable goroutines pool to bound concurrency based on semaphore.
gleam - ⭐️ A friendly language for building type-safe, scalable systems!
quinn - Async-friendly QUIC implementation in Rust
parallel-fn - Run functions in parallel :comet:
preemptible-thread - How to preempt threads in user space