| commit | e406b664ef64f94094554111a2c2d80fce891e6d | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Thu Aug 08 01:15:22 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Thu Aug 08 01:15:22 2024 +0000 |
| tree | 5efb3af62b3b26df1784dde5e4973853f0dfeae6 | |
| parent | 310e2ed6fc8f024ee9dae4c39c16b0dfc52de9ed [diff] | |
| parent | 7554aac8874ff39b87da8f0e7c304065d6c9fbf2 [diff] |
Snap for 12199973 from 7554aac8874ff39b87da8f0e7c304065d6c9fbf2 to 24Q4-release Change-Id: I057103ab93d51f4aaa9c7819439a17082fcbce16
A Futures channel-like utility to signal when a value is wanted.
Futures are supposed to be lazy, and only starting work if Future::poll is called. The same is true of Streams, but when using a channel as a Stream, it can be hard to know if the receiver is ready for the next value.
Put another way, given a (tx, rx) from futures::sync::mpsc::channel(), how can the sender (tx) know when the receiver (rx) actually wants more work to be produced? Just because there is room in the channel buffer doesn't mean the work would be used by the receiver.
This is where something like want comes in. Added to a channel, you can make sure that the tx only creates the message and sends it when the rx has poll() for it, and the buffer was empty.
want is provided under the MIT license. See LICENSE.