Explore >> Select a destination
|
You are here 
|
without.boats | ||
| | | | |
coaxion.net
|
|
| | | | | ||
| | | | |
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. | |
| | | | |
boats.gitlab.io
|
|
| | | | | Two posts ago I proposed a particular interface for shipping self-referential generators this year. Immediately after that, eddyb showed me a better interface, which I described in the next post. Now, to tie everything together, its time to talk about how we can integrate this into the futures ecosystem. Starting point: this Generator API To begin, I want to document the generator API I'll be using in this post, which is roughly what followed from my previous post: | |
| | | | |
nick.zoic.org
|
|
| | | |||
