Should we expose task::AtomicWaker?
Open
api design
feedback wanted
- Dominant language
- Rust
- Stars
- 4.1k
- Forks
- 339
- PR merge metrics
- No merged PRs in 30d
Description
As per https://github.com/async-rs/futures-timer/issues/39 it seems there are some scenarios where having an `AtomicWaker` type available would be useful.
It's somewhat niche, but I was wondering if it would perhaps make sense to expose it? Thoughts?
If we do we should probably create a separate crate so we can share the impl with `futures-timer`. Thanks!
Contributor guide
Assessment
This issue has not been assessed yet.