Explore >> Select a destination
|
You are here 
|
without.boats | ||
| | | | |
boats.gitlab.io
|
|
| | | | | This is the first in a series of blog posts about generators, async & await in Rust. By the end of this series, I will have a proposal for how we could expediently (within the next 12 months) bring generators, async & await to stable Rust, and resolve some of the most difficult ergonomics problems in the futures ecosystem. But that proposal is still several posts away. Before we can get to a concrete proposition, we need to understand the scope & nature of the problem we need to solve. | |
| | | | |
tmandry.gitlab.io
|
|
| | | | | The issue to stabilize an initial version of async/await in Rust has left final comment period. The feature looks slated to stabilize in an upcoming release, most likely 1.39. This represents the culmination of an enormous amount of work by people all over the Rust community. But it's also only the beginning of async/await support in Rust. The feature set being stabilized is a "minimum viable product" for shipping async/await, and we plan to continue to expand the feature set after initial stabilization. | |
| | | | |
theincredibleholk.org
|
|
| | | | | One of the major goals for the Rust Async Working Group is to allow async fn everywhere fn is allowed, especially in traits. In this post, I'd like to distill s... | |
| | | | |
www.hhyu.org
|
|
| | | Science, programming, books, and other interesting stuff | ||
