WG-async meeting agenda

• Meeting date: 2024-04-04

Attendance

• People: TC, tmandry, Yosh, CE, eholk

Meeting roles

• Minutes: TC

Scheduled meetings

None.

Update these here.

Proposed meetings

None.

Update these here.

Availability

Fill in your availability for the available dates here.

• 11th: AsyncIterator
  • tmandy: Out this week.
• 18th: AsyncIterator
• 25th: AsyncIterator

Otherwise everyone in attendance should be available on these dates.

Proposed topics

Propose topics for design meetings here.

• Edition coming up.
  • Migration lints for IntoFuture / Future in prelude.
  • Auto-deref for .await?
    • Maybe we don't want this after all?
• The WG-async priorities that we discussed.
  • Work on publishing a roadmap document.
• Work on async closures.
  • Work on a design document for a lang meeting.
• Remaining bikeshed on async gen / AsyncIterator / AsyncGen / Stream / etc.
• Remaining bikeshed on for await syntax.
• Becoming a team and what that would mean and the process etc.
• The ongoing work on async drop from petrochenkov et al.
• Work on maybe async / effect generics.
  • maybe-async trait definitions.
  • maybe-async functions and bounds.
  • maybe-async types.
• RTN.
  • Work on the RFC for this.
• Talk about design principles for async.

https://hackmd.io/ZDzG2sySTmm-DrAvI2j1Xw

.await autoderef

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

Consensus: Many of us have developed mixed feeling on this. We had previously made a recommendation to the lang team on this. We'll remove the nomination and retract our recommendation while we continue to think about this further. We're not highly motivated to discuss this soon.