-
Notifications
You must be signed in to change notification settings - Fork 653
Provide an atomic Task cell #361
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
Comments
Currently available at https://github.com/carllerche/futures-broadcast/blob/master/src/atomic_task.rs, we can probably clean up slightly and move in here |
This is being added in #436 |
I didn't actually expose it yet.
…On Tue, Apr 11, 2017 at 12:35 PM Alex Crichton ***@***.***> wrote:
This is being added in #436
<#436>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#361 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAYJPj9iHVYb6CLKCywnl0BV1QcA8Aoks5ru9XjgaJpZM4LmVVo>
.
|
Provided in #550 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, a number of communication structures require a mutex to store the task handle. It would be nice if there were some kind of atomic Task cell that could be used instead.
I'm not sure if this is possible (most likely not easy), but I am creating the issue to track the feature request.
The text was updated successfully, but these errors were encountered: