Tracking issue for RFC 2592, futures_api · Issue #59113 · rust-lang/rust (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

This is a tracking issue for the std::{future, task} RFC 2592 under the feature gate futures_api.

Steps:

• Implement the RFC (Update the future/task API #57992)
• Migrate futures-preview and some existing uses of it (Fuchsia) to the latest unstable API to ensure compatibility.
• Make RawWakerVTable fields private and add a const fn constructor.
• Stabilization PR (see instructions on forge)

Unresolved questions from FCP:

• Should Future::poll take &Waker or a &Context from which an &Waker can be obtained?