#asyncstd search results

My current strategy is to use a async executor runtime, like #TokioRs or #AsyncStd and use actor patterns rather than actor frameworks. All-in-one frameworks tend to freeze code design.


#asyncstd takes the right approach by fully embracing the upcoming async/.await/new-Future paradigm rather than patching new concepts on older APIs. Nice to see it uses #Crossbeam and #mio as well. Great Job! Definitely, plan to use it.

We released `async-std` 0.99.4, compatible with latest Rust nightly. Now, you can write async code without `#[feature(async_await)]`!



@FerrousSystems The talk at #rustfest was great, looking forward to integrate #asyncstd soon!


My current strategy is to use a async executor runtime, like #TokioRs or #AsyncStd and use actor patterns rather than actor frameworks. All-in-one frameworks tend to freeze code design.


@FerrousSystems The talk at #rustfest was great, looking forward to integrate #asyncstd soon!


#asyncstd takes the right approach by fully embracing the upcoming async/.await/new-Future paradigm rather than patching new concepts on older APIs. Nice to see it uses #Crossbeam and #mio as well. Great Job! Definitely, plan to use it.

We released `async-std` 0.99.4, compatible with latest Rust nightly. Now, you can write async code without `#[feature(async_await)]`!



No results for "#asyncstd"
No results for "#asyncstd"
Loading...

Something went wrong.


Something went wrong.


United States Trends