Skip to content

Add select_timeout for pipes #3016

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
eholk opened this issue Jul 25, 2012 · 5 comments
Closed

Add select_timeout for pipes #3016

eholk opened this issue Jul 25, 2012 · 5 comments
Labels
A-concurrency Area: Concurrency C-enhancement Category: An issue proposing an enhancement or a PR with one. P-low Low priority

Comments

@eholk
Copy link
Contributor

eholk commented Jul 25, 2012

Part of #1255.

This would take a list of selectables, and return an option of which one was ready (possibly going ahead and doing the receive), or none.

@ghost ghost assigned eholk Jul 26, 2012
@graydon
Copy link
Contributor

graydon commented Jun 19, 2013

This is not .. exactly done? I think. It's hard to say. I believe the subsystems in question are in the process of being rewritten under the new scheduler, but there is presently a select function in std::comm that calls wait_many. I think this needs @brson to decide if it's live or not.

@bblum
Copy link
Contributor

bblum commented Jun 21, 2013

While we have select, we don't yet have one that won't wait forever.

@emberian
Copy link
Member

emberian commented Aug 5, 2013

Visiting for triage; nothing to add

@pnkfelix
Copy link
Member

Accepting P-low.

@steveklabnik
Copy link
Member

I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized.

This issue has been moved to the RFCs repo: rust-lang/rfcs#820

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-concurrency Area: Concurrency C-enhancement Category: An issue proposing an enhancement or a PR with one. P-low Low priority
Projects
None yet
Development

No branches or pull requests

6 participants