Matt Corallo 8157c01eab Never store more than one StdWaker per live Future ... When an `std::future::Future` is `poll()`ed, we're only supposed to use the latest `Waker` provided. However, we currently push an `StdWaker` onto our callback list every time `poll` is called, waking every `Waker` but also using more and more memory until the `Future` itself is woken. Here we fix this by removing any `StdWaker`s stored for a given `Future` when it is `drop`ped or prior to pushing a new `StdWaker` onto the list when `poll`ed. Sadly, the introduction of a `Drop` impl for `Future` means we can't trivially destructure the struct any longer, causing a few methods to need to take `Future`s by reference rather than ownership and `clone` a few `Arc`s. Fixes #2874		2024-02-15 21:52:06 +00:00
..
src	Never store more than one StdWaker per live Future	2024-02-15 21:52:06 +00:00
Cargo.toml	Bump versions to LDK 0.0.121/invoice 0.29	2024-01-22 22:32:30 +00:00