WG-async triage meeting 2024-01-15

--- title: WG-async triage meeting 2024-01-15 tags: ["WG-async", "triage-meeting", "minutes"] date: 2024-01-15 discussion: https://rust-lang.zulipchat.com/#narrow/stream/187312-wg-async/topic/Triage.20meeting.202024-01-15 url: https://hackmd.io/XL1nR7KaRPeNGS6M3xOuoQ --- # WG-async meeting agenda - Meeting date: 2024-01-15 ## Attendance - People: TC, eholk, CE, Yosh ## Meeting roles - Minutes: TC ## Scheduled meetings - 2024-01-18: "Roadmap planning: 2024-01-18" [#329](https://github.com/rust-lang/wg-async/issues/329) - 2024-01-25: "Discuss `async Drop`" [#330](https://github.com/rust-lang/wg-async/issues/330) Update these [here](https://github.com/orgs/rust-lang/projects/40/views/1). ## Proposed meetings None. Update these [here](https://github.com/orgs/rust-lang/projects/40/views/1). ## Announcements or custom items (Meeting attendees, feel free to add items here!) ## Nominated RFCs, PRs, and issues ### "Tracking Issue for `task::Waker::noop`" rust#98286 **Link:** https://github.com/rust-lang/rust/issues/98286 CE: There's a recent PR that causes it to return a `&Waker`. This is better in terms of e.g. the way that const promotion works. https://github.com/rust-lang/rust/pull/119984 *Consensus*: WG-async is in favor of returning `&Waker` from the function due to ergonomic considerations related to const promotion and temporary lifetimes. We're OK with the `Waker::noop()` name for this function since we expect this is what people will need most of the time, and if we later did find that people needed an owned no-op waker (for reasons we can't imagine today) that it could receive the longer name, e.g. `Waker::noop_owned`. In our discussions, we did wonder about whether it would also make sense to add `Context::noop()` (which would return an owned `Context`) which would shorten the most common use-case further. ### "Tracking Issue for `Ready::into_inner()`" rust#101196 **Link:** https://github.com/rust-lang/rust/issues/101196 TC: We're waiting for use cases, as is T-libs-api. But there's an open question on naming. Yosh: I agree with the argument TC put forward. *Consensus*: WG-async would like to see example use cases, either of the proposed standard library version or the one in `futures-rs`. ### "Add `AsyncFn` family of traits" rust#119305 **Link:** https://github.com/rust-lang/rust/pull/119305 errs: This is stalled; I'm probably going to add lending fns instead. ### "Add LocalWaker support" libs-team#191 **Link:** https://github.com/rust-lang/libs-team/issues/191 CE: We may want to unnominate this until there's more to review. TC: When do we want this renominated for us? CE: Probably when there's a design. *Consensus*: Let's unnominate and ask for this to be renominated for us when there is a revised design here. ### "Rename `AsyncIterator` back to `Stream`, introduce an AFIT-based `AsyncIterator` trait" rust#119550 **Link:** https://github.com/rust-lang/rust/pull/119550 CE: We should discuss this soon. *Consensus*: Let's bump the Zulip thread on this and see whether we can find a consensus there or need to schedule a time for this. ## Untriaged issues ### "ICE with "failed to resolve instance for <... as IntoFuture>::into_future: Ok(None)" (regression between 1.73 and 1.74)" rust#119095 **Link:** https://github.com/rust-lang/rust/issues/119095 ### "Add `AsyncFn` family of traits" rust#119305 **Link:** https://github.com/rust-lang/rust/pull/119305 See above ### "ice: `async fn coroutine return type not an inference variable`" rust#119890 **Link:** https://github.com/rust-lang/rust/issues/119890 ### "Add LocalWaker support" libs-team#191 **Link:** https://github.com/rust-lang/libs-team/issues/191 ## WG RFCs, PRs, and issues nominated for T-lang/T-types ### "`.await` does not perform autoref or autoderef" rust#111546 **Link:** https://github.com/rust-lang/rust/issues/111546 ## Pending PRs on the WG-async repo None. ## `S-waiting-on-team` ### "Rename `AsyncIterator` back to `Stream`, introduce an AFIT-based `AsyncIterator` trait" rust#119550 **Link:** https://github.com/rust-lang/rust/pull/119550 ## Proposed FCPs **Check your boxes!** ### "Tracking Issue for `Ready::into_inner()`" rust#101196 **Link:** https://github.com/rust-lang/rust/issues/101196 ## Active FCPs None. ## P-critical issues None. ## WG-async work project board https://github.com/orgs/rust-lang/projects/29/views1/d