lunatic
async-std
lunatic | async-std | |
---|---|---|
1 | 19 | |
1,026 | 3,945 | |
- | 0.8% | |
7.6 | 6.4 | |
over 3 years ago | 22 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | 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.
lunatic
-
Writing Rust the Elixir way
This is just a teaser of the capabilities that Lunatic will provide. There are many more features coming. Once you have this foundation, a new world of possibilities opens up. Some of the features I'm excited about:
async-std
-
Stabilizing async fn in traits in 2023 | Inside Rust Blog
But maybe check out the discussion here https://github.com/async-rs/async-std/pull/631 or something (the blog post was linked on the end of it)
-
Anyone using io_uring?
Have a look at these: https://github.com/async-rs/async-std/tree/main/examples
-
Any plans for built-in support of Vec2/Vec3/Vec4 in Rust?
In fact, there are a lot of crates in Rust where in other programming languages, it would be included in the standard library. Examples are regex, random number generators, additional iterator methods, macros for other collections, num traits, loggers, HTTP libraries, error handling, async runtimes, serialization and deserialization, date and time, and many more.
-
18 factors powering the Rust revolution, Part 2 of 3
Two major projects (non std lib but extremely commonly used) stand out in the area of async programming: Async std and Tokio - no doubt familiar to anyone that has turned an eye towards Rust for a second too long. Async architecture in general is likely very familiar to JavaScript programmers but in Rust there are some extra considerations (like ownership of the data that is thrown into an async function). Tokio is fast becoming a heavily supported and road tested async framework, with a thread scheduling runtime "baked in" that has learned from the history of Go, Erlang, and Java thread schedulers.
-
What are the side-effects of using different runtimes in the same codebase?
Ah... https://github.com/tokio-rs/tokio and https://github.com/async-rs/async-std ?
-
Hey Rustaceans! Got an easy question? Ask here (51/2021)!
async-std: Basically a Tokio alternative with a few different design decisions.
-
Why asynchronous Rust doesn't work
Go's solution is for the scheduler to notice after a while when a goroutine has blocked execution and to shift goroutines waiting their turn to another thread. async-std pondered a similar approach with tasks, but it proved controversial and was never merged.
-
Building static Rust binaries for Linux
This indicates curl, zlib, openssl, and libnghttp2 as well as a bunch of WASM-related things are being dynamically linked into my executable. To resolve this, I looked at the build features exposed by surf and found that it selects the "curl_client" feature by default, which can be turned off and replaced with "h1-client-rustls" which uses an HTTP client backed by rustls and async-std and no dynamically linked libraries. Enabling this build feature removed all -sys dependencies from androidx-release-watcher, allowing me to build static executables of it.
-
Rust async is colored, and that’s not a big deal
And also, the actual PR never got merged.
-
Rust's async isn't f#@king colored!
Async in rust needs a runtime (aka executor) to run. You can maybe get a better description from the rust docs. As an example, Tokio attempts to provide an interface for a developer that is minimal change to the more common blocking code. So you'd end up putting #[tokio::main] above your main function to spin up the executor and most of the rest of the code is similar to a non-async version with a few sprinkles of .await, which you can see in the hello world for tokio. In contrast, async-std provides a more hands-on/low-level approach. If you are unlucky enough to have libraries that choose different stacks to work on, you'll possibly (probably?) have to handle both.
What are some alternatives?
lucet - Lucet, the Sandboxing WebAssembly Compiler.
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
libfringe - a Rust library implementing safe, lightweight context switches, without relying on kernel services
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
smol - A small and fast async runtime for Rust
futures-rs - Zero-cost asynchronous programming in Rust
reqwest - An easy and powerful Rust HTTP Client
embassy - Modern embedded framework, using Rust and async.
async-std-hyper - How to run Hyper on async-std
async-tungstenite - Async binding for Tungstenite, the Lightweight stream-based WebSocket implementation
hyper - An HTTP library for Rust