Implement rendezvous mpsc channel #57

Activity

1. tisonkun

   added

   enhancementNew feature or requestNew feature or request

   help wantedExtra attention is neededExtra attention is needed

   good first issueGood for newcomersGood for newcomers

   on Jun 24, 2025
2. tisonkun commented on Jul 8, 2025

   

   tisonkun

   on Jul 8, 2025

   MemberAuthor

   More actions

   After a closer look, in Async Rust, this is somehow the same as buffer = 1.

   Take futures-channel's impl as an example:

   let (tx, mut rx) = ...;
   tx.try_send(1);
   rx.try_recv().unwarp(); // Some(1)

   This is because, if the whole program consist by try_send and recv, it should be able to send/recv. But in Async Rust, even if the send puts the value to an intermediate buffer, and wakes up the recv task, the recv task may not be scheduled or run.

   So, I'd suggest people who wants to use a rendezvous mpsc channel just create a bounded channel with buffer = 1. The difference is tiny and can be ignored.
3. tisonkun

   closed this as not plannedon Jul 8, 2025
4. tisonkun commented on Aug 21, 2026

   

   tisonkun

   on Aug 21, 2026

   MemberAuthor

   More actions

   Superseded by #167. The new design treats rendezvous as an explicit handoff contract: send completes only after a receive operation accepts the value, which is distinct from enqueueing into a capacity-one buffer. Keeping this issue closed in favor of the broader design tracker.