Explore >> Select a destination
|
You are here 
|
boats.gitlab.io | ||
| | | | |
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. | |
| | | | |
without.boats
|
|
| | | | | [AI summary] The blog post discusses the challenges and limitations of using generators and async/await in Rust, focusing on issues with borrowing and self-referential structs, and their impact on the futures ecosystem. | |
| | | | |
qsantos.fr
|
|
| | | | | Although I am now mostly comfortable with Rust, some concepts still elude me. One of them is the exact meaning of Unpin. The documentation says: The documentation of Unpin says: Types that do not require any pinning guarantees. Where pinning is described as: From this, you could naturally deduce that Unpin is the trait that ... Continue reading You can move !Unpin ? | |
| | | | |
www.ralfj.de
|
|
| | | |||
