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

Release and deprecate rayon-futures 0.1.1 #715

Merged
merged 12 commits into from
Dec 21, 2019

Conversation

cuviper
Copy link
Member

@cuviper cuviper commented Dec 19, 2019

This includes the soundness fix from #698, just targeted to a new branch.

jClaireCodesStuff and others added 11 commits September 18, 2019 17:02
…w rejected by a compiler

error.

`Sync` and `Send` are now derived by the compiler for `ScopeFuture`, except that the
`Send`-safety of `impl ScopeHandle` is is still asserted unsafety.  I did not review `rayon_core`
to judge whether that is correct.
Merge branch 'issue-697' of github.com:jClaireCodesStuff/rayon into issue-697
@cuviper
Copy link
Member Author

cuviper commented Dec 21, 2019

bors r+

bors bot added a commit that referenced this pull request Dec 21, 2019
715: Release and deprecate rayon-futures 0.1.1 r=cuviper a=cuviper

This includes the soundness fix from #698, just targeted to a new branch.

Co-authored-by: J Claire <[email protected]>
Co-authored-by: Josh Stone <[email protected]>
@bors
Copy link
Contributor

bors bot commented Dec 21, 2019

@bors bors bot merged commit 30c50de into rayon-rs:rayon-futures-0.1.x Dec 21, 2019
bors bot added a commit that referenced this pull request Dec 21, 2019
716: Release rayon 1.3.0 / rayon-core 1.7.0 r=cuviper a=cuviper

This also removes `rayon-futures` and `cfg(rayon_unstable)` -- see #715 for their deprecation.

Co-authored-by: Josh Stone <[email protected]>
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.

2 participants