Tracking Issue for mpmc

[obeis]

Feature gate: #![feature(mpmc_channel)]

This is a tracking issue for mpmc_channel as described in ACP.

History

• ACP
• Implementation: Add multi-producer, multi-consumer channel (mpmc) #126839
• Final comment period (FCP)
• Stabilization PR

[ora-0]

The sync::mpsc module's sync_channel function returned a SyncSender and SyncReceiver type, but the new mpmc module's sync_channel returns just a normal Sender and Receiver type. Is this symmetry something we want to preserve?

This shouldn't affect any usage of them, except for the slightly different documentation provided.

[ibraheemdev]

I wonder if there's a downside to SyncSender and Sender being separate types, and you would ever need to create an enum (which is unnecessary because they are internally enum) to switch between them dynamically. This seems unlikely as they have different semantics, but theoretically if you are only using try_send you may want to. I think this is less of a concern than keeping the modules consistent, but the SyncSender naming is itself confusing, so I'm not sure.