Twitter | Pretraživanje | |
async-std
Don't let anyone block you! We're introducing a new adaptive, -inspired, async runtime that automatically detects blocking behaviour and just continues to run and run. Don't worry about separate blocking and non-blocking tasks anymore!
Reply Retweet Označi sa "sviđa mi se" More
async-std 16. pro
Odgovor korisniku/ci @dieselframework
The new runtime also allows you to use mature sync libraries like without fear! No need to manage a secondary threadpool for blocking tasks! On top of that, the new runtime is also much better at scaling down, effectively becoming single-threaded if possible.
Reply Retweet Označi sa "sviđa mi se"
async-std 16. pro
Odgovor korisniku/ci @asyncrs
So, how about speed? The new runtime is faster over 1.3.0, especially scaling much better. How do you use it? Just try out our current PR branch, instructions are in the blog post. async-std is fully compatible to futures-rs, for your ease!
Reply Retweet Označi sa "sviđa mi se"
Leo Dutra 16. pro
Odgovor korisniku/ci @asyncrs @golang @rustlang
Wow, this is awesome. Thanks.
Reply Retweet Označi sa "sviđa mi se"
async-std 16. pro
Odgovor korisniku/ci @leodutra @golang @rustlang
🙇‍♂️ It's a pleasure!
Reply Retweet Označi sa "sviđa mi se"
Adil H 16. pro
Odgovor korisniku/ci @asyncrs @golang @rustlang
"The runtime measures the time it takes to perform the blocking operation and if it takes a while, a new thread is automatically spawned" ... would love a more detailed blog post explaining how this actually works
Reply Retweet Označi sa "sviđa mi se"
async-std 16. pro
Odgovor korisniku/ci @le_didil @golang @rustlang
Coming up down the line. But essentially, its the `sysmon` from this:
Reply Retweet Označi sa "sviđa mi se"
Rafał Cieślak 16. pro
Odgovor korisniku/ci @asyncrs
Does it actually make the problem described in “What Color Is Your Function” disappear? 🤔 I pretty much don’t know Rust, but I see that you still have to use an async function.
Reply Retweet Označi sa "sviđa mi se"
async-std 16. pro
Odgovor korisniku/ci @Ravicious
It makes the problem of calling sync functions within async functions. async function in Rust still have specific meaning (they are used to generate Futures, which you can execute). But that problem is rather inherent, but also not so painful.
Reply Retweet Označi sa "sviđa mi se"
Andy 🦀⚙️ 16. pro
Odgovor korisniku/ci @asyncrs @golang @rustlang
Not gonna lie, this reads kinda like an April Fools Day post
Reply Retweet Označi sa "sviđa mi se"
Markus A. 16. pro
Odgovor korisniku/ci @asyncrs
Interesting! Not just for blocking tasks, but also for potentially long running ones where it is hard to decide whether they are better offloaded to a thread pool or not 🧐. Seems like I finally have a reason to give a try (instead of using Tokio as I am used to).
Reply Retweet Označi sa "sviđa mi se"