Skip to content

Non-Send boxed() #1563

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

Merged
merged 5 commits into from
May 2, 2019
Merged

Non-Send boxed() #1563

merged 5 commits into from
May 2, 2019

Conversation

chmln
Copy link
Contributor

@chmln chmln commented Apr 27, 2019

This PR adds non-Send versions of BoxFuture and boxed(), prompted by the Send requirement in #1494 (and thus the latest release) breaking some of our code. This allows avoiding unnecessary Send bounds in generic-heavy code.

@overdrivenpotato
Copy link
Contributor

Dealing with the same issue here.

@cramertj Is it possible to simply revert the boxed changes in #1494? The new alpha 15 release today broke several of my projects, requiring hefty propagation of Send throughout many modules. Specifically, is there a reason why this change was necessary?

@Nemo157
Copy link
Member

Nemo157 commented Apr 27, 2019

The CI failure is related to #1555 and rust-lang/rust#60289, I'm looking into a fix for it.

EDIT: Opened #1564 to track it.

miquels added a commit to miquels/webdav-handler-rs that referenced this pull request Apr 30, 2019
In futures 0.3.alpha15, the .boxed() helper added a Send trait bound.
As we don't need that, use Box::pin instead. alpha16 will likely
have a .boxed_local() helper. See also
rust-lang/futures-rs#1563
@cramertj cramertj merged commit 31948bd into rust-lang:master May 2, 2019
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