You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/2025h1/async.md
+36-11Lines changed: 36 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Despite async Rust's popularity, using async I/O makes Rust significantly harder
30
30
31
31
* Common language features do not support async, meaning that [users cannot write Rust code in the way they are accustomed to](https://rust-lang.github.io/wg-async/vision/submitted_stories/status_quo/barbara_plays_with_async.html?highlight=closure#the-story):
32
32
*[x]~~[traits](https://rust-lang.github.io/wg-async/vision/submitted_stories/status_quo/alan_needs_async_in_traits.html)~~ (they [do now][afitblog], though gaps remain)
33
-
*[x] closures (about to [stabilize](https://github.com/rust-lang/rust/pull/132706))
In many cases there are workarounds or crates that can close the gap, but users have to learn about and find those crates.
36
36
* Common async idioms have "sharp edges" that lead to unexpected failures, forcing users to manage [cancellation safety](https://rust-lang.github.io/wg-async/vision/submitted_stories/status_quo/barbara_gets_burned_by_select.html), subtle [deadlocks](https://rust-lang.github.io/wg-async/vision/submitted_stories/status_quo/aws_engineer/solving_a_deadlock.html) and other failure modes for [buffered streams](https://rust-lang.github.io/wg-async/vision/submitted_stories/status_quo/barbara_battles_buffered_streams.html). See also tmandry's blog post on [Making async Rust reliable](https://tmandry.gitlab.io/blog/posts/making-async-reliable/)).
@@ -51,13 +51,18 @@ Despite async Rust's popularity, using async I/O makes Rust significantly harder
51
51
#### Improve ergonomics around `Pin`
52
52
53
53
* Ratify and implement an RFC for auto-reborrowing of pinned references
54
-
* Stretch goal: Ratify an RFC for safe pin projection
54
+
* Stretch goal: Discuss and implement a design for safe pin projection
55
55
56
56
#### Work toward asynchronous generators
57
57
58
-
* Ratify an RFC for synchronous generators
59
-
* Review 1-2 RFCs for asynchronous iteration trait with the lang and libs-api teams and decide on the core trait to be stabilized
60
-
* Stretch goal: Ratify an RFC for unsafe binders and RTN in type position
58
+
* Have design meetings and ratify an RFC for synchronous generators
59
+
* Have a design meeting for asynchronous iteration
60
+
* Stretch goal: Ratify an RFC for unsafe binders
61
+
62
+
In H2 we hope to tackle the following:
63
+
64
+
* RTN in type position
65
+
* Ratified RFC for asynchronous iteration
61
66
62
67
### The "shiny future" we are working towards
63
68
@@ -98,6 +103,14 @@ This section defines the specific work items that are planned and who is expecte
0 commit comments