| commit | 310e2ed6fc8f024ee9dae4c39c16b0dfc52de9ed | [log] [tgz] |
|---|---|---|
| author | Frank Piva <[email protected]> | Fri Jun 07 11:06:20 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Fri Jun 07 11:06:20 2024 +0000 |
| tree | 0ebf1cbe148a67ad9b109b9a07851d6ebd5dff24 | |
| parent | 3b603739415fee5b383fa9d67cafc2b682ac141e [diff] | |
| parent | 3c3c2a56aba68814d5cc94801922fb108d6fd886 [diff] |
Merge remote-tracking branch 'origin/upstream' am: 93e24a1529 am: 3c3c2a56ab Original change: undetermined Change-Id: I96ea8b8846bfad4cb15a1906407f7a5fcae6da48 Signed-off-by: Automerger Merge Worker <[email protected]>
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.