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

Cargo cannot install crate? #1052

Closed
akshaynanavati opened this issue Jun 28, 2018 · 3 comments
Closed

Cargo cannot install crate? #1052

akshaynanavati opened this issue Jun 28, 2018 · 3 comments

Comments

@akshaynanavati
Copy link

I have futures = "0.2.1" in my cargo.toml, yet I get the following when I try to build:

Updating registry `https://github.com/rust-lang/crates.io-index`
error: no matching version `^0.2` found for package `futures`
location searched: registry `https://github.com/rust-lang/crates.io-index`
versions found: 0.1.21, 0.1.20, 0.1.18, ...

Cargo version:

$ cargo --version
cargo 1.28.0-nightly (e2348c2db 2018-06-07)

Any help would be appreciated.

@MajorBreakfast
Copy link
Contributor

Version 0.2 has been yanked from the fututres crate. It has been republished as the futures-preview crate.

#1039

I am sure that this will be communicated widely soon. This issue should best be kept open until that happened so that other people can easily find it.

@akshaynanavati
Copy link
Author

Thanks. Is there a more recent version of futures in the nightly build, should I instead use futures 0.1.x, or should I use futures-preview? I'd like to use the one that is most recent and closest to being standardized (if this is possible).

@MajorBreakfast
Copy link
Contributor

MajorBreakfast commented Jun 28, 2018

In that case I recommend using the 0.3 branch. It's not yet available on crates.io and currently in pre-alpha state, but most of it already works. Just don't trust any descriptions in the documentation, because in most cases only the code examples were updated to make them compile ;-)

Edit: futures-core 0.3 just reexports the stuff from libcore (plus defines some stuff like Stream). So, it includes exactly what's about to be standardized :P

Edit: Again, don't close this issue until there was a proper announcement about the fate of 0.2

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

3 participants