StreamExt::buffered and StreamExt::buffer_unordered hangs (again) for n = 0

[LeoniePhiline]

There was a "fix" (panic - not preferred) in the past:

• StreamExt::buffered and StreamExt::buffer_unordered hangs for n = 0 #2348
• https://github.com/rust-lang/futures-rs/pull/2364/files

This assert! was later removed:

• 3ee42c6#diff-e1651bc6e1531ad82dfb2571a0d2eb180c1567085cbec9934d66a17fb140e38cR44-R55 (part of allow no limit for buffered stream combinators #2429)

I am not sure if this was intentional.

The following project hangs indefinitely:

Cargo.toml

[package]
name = "buffered"
version = "0.1.0"
edition = "2021"

[dependencies]
futures = "0.3.28"
tokio = { version = "1.28.0", features = ["macros", "rt-multi-thread"] }

src/main.rs

use futures::prelude::*;

#[tokio::main]
async fn main() {
    // Assume not knowing the length of this vec in advance.
    let v: Vec<i32> = vec![];

    // Length might be 0.
    let num_concurrent = v.len();

    // Process all in parallel.
    let w = futures::stream::iter(v.into_iter())
        .map(|e| async move {
            // "Processing" ...
            e
        })
        // Process all entries concurrently
        .buffered(num_concurrent)
        .collect::<Vec<i32>>()
        .await;

    // Never finishes.

    println!("{w:#?}"); // Never prints.
}

With a minimum buffered value of 1, the program finishes.

I believe n = 0 should not panic, as the old assert! solution did, but it should pass through directly without buffering.

(Could be worked around by lower-clamping n to 1 in Buffered::new, but I am certain there is a cleaner way.)

[taiki-e]

Both fixes are included in 0.4, not 0.3 that you are using.

[LeoniePhiline]

@taiki-e There is no 0.4?

Not on GitHub releases, no branch, no tag, not on crates.io, not in the futures-rs blog …

Where is 0.4 and why can’t I find it?

[krakow10]

I'm having this exact issue, 0.4 does not exist?

[BatmanAoD]

@LeoniePhiline @krakow10 The master branch is 0.4.

@taiki-e Is there any sort of plan for when 0.4 might be tagged/released, and is there any way to track progress towards that? I see the 1.0 milestone ticket, but the last comment there is over 4 years ago. It seems like it would probably be useful to have 0.4-alpha released, even if the stable release is still some years off.