---
title: WG-async planning/triage meeting 2024-06-06
tags: ["WG-async", "planning-meeting", "triage-meeting", "minutes"]
date: 2024-06-06
discussion: https://rust-lang.zulipchat.com/#narrow/stream/187312-wg-async/topic/Planning.20meeting.202024-06-06
url: https://hackmd.io/ovFJvnNpRP2gP-ZJYmfqgg
---

# WG-async meeting agenda

- Meeting date: 2024-06-06

## Attendance

- People: TC, tmandry, Yosh, eholk, Daria

## Meeting roles

- Minutes:

## Scheduled meetings

None.

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!)

## Untriaged issues

### "Weird type inference around impl Trait and async" rust#124757

**Link:** https://github.com/rust-lang/rust/issues/124757

CE has said this is a duplicate, probably of:

https://github.com/rust-lang/rust/issues/110339

That one was filed by tmandry.

We think it's probably a duplicate of some issue, but we're not sure which, so we've added it to the list.

### "Poor interaction between NLL-borrowck, async, and c_variadic's `...` desugaring (`VaListImpl<'_>`)" rust#125431

**Link:** https://github.com/rust-lang/rust/issues/125431

We can't reproduce this in nightly, so maybe it's fixed?

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=37080445a38892d4fc9d2ada04f78a20

### "Unhelpful error on mismatched types for anonymous futures" rust#125737

**Link:** https://github.com/rust-lang/rust/issues/125737

We agreed and left a comment.

### "Add LocalWaker support" libs-team#191

**Link:** https://github.com/rust-lang/libs-team/issues/191

We'd like to see some use cases. We're also interested here in the interaction between this and `LocalFuture` and whether we would want that.

I.e., is `LocalWaker` useful if there's no guarantee that your future can't move across threads?

Back on 2024-04-08, we unnominated this item in favor of reviewing it ahead of stabilization.

### "Context reactor hook" libs-team#347

**Link:** https://github.com/rust-lang/libs-team/issues/347

Here's Josh's comment on it:

https://github.com/rust-lang/rust/pull/123203#issuecomment-2032461923

FCP for `Error` in core started last week:

https://github.com/rust-lang/rust/issues/103765

The nuclear option is to make `Future` generic on context, and have it default to the current `Context`.

## Planning

Thursdays this month:

- 6th (today).
- 13th
- 20th
- 27th

We'll fill these in with open discussion.

## Nominated RFCs, PRs, and issues

### "Generic Futures" rfcs#3434

**Link:** https://github.com/rust-lang/rfcs/pull/3434

This relates to the above actually. We'd probably make them generic over contexts rather than over wakers as this RFC seems to do.

We could either make context generic over waker or future generic over context.

(The meeting ended here.)

---

### "Tracking Issue for `waker_getters`" rust#96992

**Link:** https://github.com/rust-lang/rust/issues/96992

### "Tracking Issue for `task::Waker::noop`" rust#98286

**Link:** https://github.com/rust-lang/rust/issues/98286

### "Tracking Issue for `Ready::into_inner()`" rust#101196

**Link:** https://github.com/rust-lang/rust/issues/101196

### "Tracking Issue for `const_waker`" rust#102012

**Link:** https://github.com/rust-lang/rust/issues/102012

### "Rename `AsyncIterator` back to `Stream`, introduce an AFIT-based `AsyncIterator` trait" rust#119550

**Link:** https://github.com/rust-lang/rust/pull/119550

### "Clarification needed on what happens when `Future::poll` wakes an old waker" rust#119698

**Link:** https://github.com/rust-lang/rust/issues/119698

### "Context reactor hook" libs-team#347

**Link:** https://github.com/rust-lang/libs-team/issues/347

## WG RFCs, PRs, and issues nominated for T-lang/T-types

### "Initial support for auto traits with default bounds" rust#120706

**Link:** https://github.com/rust-lang/rust/pull/120706

## 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

### "Tracking Issue for `const_waker`" rust#102012

**Link:** https://github.com/rust-lang/rust/issues/102012

## Active FCPs

None.

## P-critical issues

None.

## WG-async work project board

https://github.com/orgs/rust-lang/projects/29/views1/d