rust-lang / rust-lang/rust

Tracking issue for `Waker::from_fn_ptr`

Open
#148,457 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue S-tracking-unimplemented T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Feature gate: #![feature(waker_from_fn_ptr)]

Public API
// core::task

impl Waker {
    pub const fn from_fn_ptr(f: fn()) -> Self;
}

impl LocalWaker {
    pub const fn from_fn_ptr(f: fn()) -> Self;
}
Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

Unresolved Questions
  • None yet.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the public API shown in this issue, then review the linked implementation PR and the feature lifecycle stabilization guide. The tracking work is complete when the final comment period and stabilization PR have been completed for both Waker::from_fn_ptr and LocalWaker::from_fn_ptr.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.