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

Make futures crate public #2

Closed
manuels opened this issue May 16, 2018 · 1 comment
Closed

Make futures crate public #2

manuels opened this issue May 16, 2018 · 1 comment

Comments

@manuels
Copy link

manuels commented May 16, 2018

You run into a problem if you want to use futures v0.1 and futures v0.2 in the same program: Cargo will only allow you to use one of them because of the name clash (I am talking about futures v0.2, not futures-core v0.2).

You could circumvent this problem if futures-compat would change a single line in lib.rs:

- extern crate futures;
+ pub extern crate futures;

In that case the programmer could use these dependencies for his programm:

[dependencies]
futures-compat = "*"
futures = "0.2.1"

and still use both Future types in the program (including async and await macros):

extern crate futures_compat;
extern crate futures;

use futures_compat::futures::Future as Future1;
use futures::Future as Future2;
@manuels
Copy link
Author

manuels commented May 16, 2018

You can forget about it: I just created a mirror crate for futures v0.1.x: https://crates.io/crates/futures-v01x

@manuels manuels closed this as completed May 16, 2018
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

No branches or pull requests

1 participant