Tracking Issue for waker_fn
Open
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_fn)]
This is a tracking issue for https://github.com/rust-lang/libs-team/issues/702.
Public API
pub fn waker_fn<F: Fn() + Send + Sync + 'static>(f: F) -> Waker {
Waker::from(Arc::new(WakeFn(f)))
}
struct WakeFn<F> {
f: F,
}
impl<F> Wake for WakeFn<F>
where F: Fn()
{
fn wake(self: Arc<Self>) { (self.f)() }
fn wake_by_ref(self: &Arc<Self>) { (self.f)() }
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: https://github.com/rust-lang/libs-team/issues/702
- Implementation: https://github.com/rust-lang/rust/pull/149976
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked libs-team issue 702 and implementation pull request 149976, then review the feature lifecycle guidance linked in the issue. The remaining work is the final comment period and a stabilization PR; done means the feature has cleared FCP and is ready for stabilization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100