You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 30, 2019. It is now read-only.
I'd like to bring rust-lang/futures-rs#800 to the attention of the WG. I won't reproduce the entire content of the issue here, but the short version is that the current bounded mpsc channel in futures-rs is difficult to use while preserving back-pressure.
That issue left off with a PoC channel implementation that does a better job at enforcing back-pressure, and shouldn't have much of an effect otherwise on the API or performance. The hope is that proof of concept can serve as the basis or inspiration for overhauling the current version in futures-rs.
Hopefully this is in the purview of the WG, because I think it's a critical component for building robust async systems!
The text was updated successfully, but these errors were encountered:
This is for sure within scope! In general I don't think our backpressure story is fully baked.
(The futures team has been primarily focused on the 0.3 work of getting the core Future and Stream traits ready for async/await, but this can absolutely proceed in parallel)
Hi all,
I'd like to bring rust-lang/futures-rs#800 to the attention of the WG. I won't reproduce the entire content of the issue here, but the short version is that the current bounded mpsc channel in
futures-rs
is difficult to use while preserving back-pressure.That issue left off with a PoC channel implementation that does a better job at enforcing back-pressure, and shouldn't have much of an effect otherwise on the API or performance. The hope is that proof of concept can serve as the basis or inspiration for overhauling the current version in
futures-rs
.Hopefully this is in the purview of the WG, because I think it's a critical component for building robust async systems!
The text was updated successfully, but these errors were encountered: