Kevin Reid 6f8a944ba4 Change return type of unstable Waker::noop() from Waker to &Waker. ... The advantage of this is that it does not need to be assigned to a variable to be used in a `Context` creation, which is the most common thing to want to do with a noop waker. If an owned noop waker is desired, it can be created by cloning, but the reverse is harder. Alternatively, both versions could be provided, like `futures::task::noop_waker()` and `futures::task::noop_waker_ref()`, but that seems to me to be API clutter for a very small benefit, whereas having the `&'static` reference available is a large benefit. Previous discussion on the tracking issue starting here: https://github.com/rust-lang/rust/issues/98286#issuecomment-1862159766		2024-01-17 11:53:16 -08:00
..
mod.rs	remove unstable Poll::ready	2023-05-19 12:42:58 +02:00
poll.rs	remove redundant imports	2023-12-10 10:56:22 +08:00
ready.rs	remove unstable Poll::ready	2023-05-19 12:42:58 +02:00
wake.rs	Change return type of unstable Waker::noop() from Waker to &Waker.	2024-01-17 11:53:16 -08:00