tokio-process
can't coexist with tokio
#27
Comments
Thanks for the report! Once futures 0.2 is published I plan on updating. |
@alexcrichton on an unrelated note, is the plan to release |
@ipetkov oh isn't this lib currently at 0.1?, making the futures 0.2 compatible release 0.2? |
Unfortunately we've got a published, but yanked, 0.2 version. Releasing a new 0.2.x version will have breaking changes relative to 0.2.0 and will probably cause more problems for anyone that happens to be on 0.2.0. I figured jumping directly to 0.3 will just bypass any of these headaches and start over! |
Oh I was gonna publish 0.2.1, while technically breaking I can't imagine anyone's actually relying on 0.2.0 |
Fair enough, will trust your judgement here, thanks! |
What's the story here now that futures 0.2 is out? |
@tarcieri I've created a milestone for tracking changes for a 0.2.x release |
Thanks @ipetkov! I wonder, does Tokio support futures 0.2 yet? |
Yes, with the |
FWIW, according to tokio-rs/tokio#312 the "recommendation from the futures team is to not update libraries fully to 0.2", given that futures 0.3 is on the horizon. |
What's the path forward here? I think some of the comments in the OP are incorrect:
The The problem is the |
Yes, I believe that's true. I must have just missed that on my first time through — I guess the port is easier than I anticipated then. |
Fine by me. |
tokio-core
is now deprecated, and the newtokio
crate has a completely different model for execution. Notably, there is AFAICT no way to get atokio_core::reactor::Handle
or anything similar fromtokio
, which makes many oftokio-process
's functions uncallable.The text was updated successfully, but these errors were encountered: