Skip to content
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

Deprecate std::sync::TaskPool #22427

Closed
wants to merge 1 commit into from

Conversation

aturon
Copy link
Member

@aturon aturon commented Feb 17, 2015

Rather than stabilize on the current API, we're going to punt this
concern to crates.io, to allow for faster iteration.

[breaking-change]

r? @alexcrichton

@aturon
Copy link
Member Author

aturon commented Feb 17, 2015

cc @reem @sfackler

@reem
Copy link
Contributor

reem commented Feb 17, 2015

Rather than stabilize on the current API, we're going to punt this
concern to crates.io, to allow for faster iteration.

If you need this functionality, you might look at https://github.com/carllerche/syncbox

[breaking-change]
@aturon aturon force-pushed the deprecate-taskpool branch from ed0cb96 to efd2a17 Compare February 17, 2015 00:42
@aturon
Copy link
Member Author

aturon commented Feb 17, 2015

@reem done

@huonw
Copy link
Member

huonw commented Feb 17, 2015

It seems like someone could copy this code out into a standalone crate onto crates.io, to give users a drop-in replacement for now?

@reem
Copy link
Contributor

reem commented Feb 17, 2015

@huonw The new thread semantics make it really tricky to actually use, so I don't think that would be very helpful.

@alexcrichton
Copy link
Member

I too agree with @huonw that if we are deprecating in favor of another implementation it should probably be a drop in replacement (and up-to-date on crates.io)

@aturon
Copy link
Member Author

aturon commented Feb 17, 2015

Ok, no real harm (though we'll eventually want to garbage collect these, somehow...)

I'll get it set up, and we can wait to land this until I have a link to point to :-)

@alexcrichton
Copy link
Member

Continuing in #22783

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants