Repository navigation
Tracking issue for mpsc::Receiver::try_iter #34931
Description
Activity
Hey folks, just thought I'd ping this and ask if there's anything I can do to help guide this towards stable? Would love to start using it, but no worries if it's just low on the priority list 👍
Reacted by Gabriel Castro, geemili and Luc FuestonI'd like to know the same thing as mitchmindtree. Is this being guide towards stable?
@rfcbot fcp merge
Seems like a nifty API to have!
Team member @alexcrichton has proposed to merge this. The next step is review by the rest of the tagged teams:
No concerns currently listed.
Once these reviewers reach consensus, this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!
See this document for info about what commands tagged team members can give me.
🔔 This is now entering its final comment period, as per the review above. 🔔
psst @alexcrichton, I wasn't able to add the
final-comment-periodlabel, please do so.The final comment period is now complete.
Tracking issue for the new non-blocking
mpsc::Receiveriterator API introduced in #34724.The API is currently gated behind the unstable
receiver_try_iterfeature.The API includes:
std::sync::mpsc::Receiver::try_iterstd::sync::mpsc::TryItercc @alexcrichton