Tracking issue for `mpsc::Receiver::try_iter`

[mitchmindtree]

Tracking issue for the new non-blocking mpsc::Receiver iterator API introduced in #34724.

The API is currently gated behind the unstable receiver_try_iter feature.

The API includes:

• std::sync::mpsc::Receiver::try_iter
• std::sync::mpsc::TryIter

cc @alexcrichton

[mitchmindtree]

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 👍

[leroycep]

I'd like to know the same thing as mitchmindtree. Is this being guide towards stable?

[alexcrichton]

@rfcbot fcp merge

Seems like a nifty API to have!

[rfcbot]

Team member @alexcrichton has proposed to merge this. The next step is review by the rest of the tagged teams:

• @BurntSushi
• @Kimundi
• @alexcrichton
• @aturon
• @brson
• @sfackler

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.

[rfcbot]

🔔 This is now entering its final comment period, as per the review above. 🔔

psst @alexcrichton, I wasn't able to add the final-comment-period label, please do so.

[rfcbot]

The final comment period is now complete.