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
Provide better way for API users to deal with unstable features #6113
Comments
I guess this is related: kbknapp/cargo-outdated#141 But I've tried the workaround from there (calling |
This isn't a bug in The problem here is that the version of The beta channel of Cargo is different source code than what's published on crates.io, only the stable channel's This isn't a problem purely isolated to This won't be a bulletproof solution but it would hopefully be a better solution than what we have now! For the time being there's unfortunately not a great solution otherwise that I know of :( |
See kbknapp/cargo-outdated#141 which is relevant, specifically cargo-outdated needs to carry the |
@joelgallant I believe that's the same issue as this one, which should be solved by my above comment |
work-around (nasty one): comment out the edition line in Cargo.toml, run |
I have the same problem with cargo-tree |
Sounds like it would be an escape hatch that would undermine the point of having unstable features. From the conversation in sfackler/cargo-tree#56 I wonder if we can either:
|
Just for reference [Solved]: I had a similar problem:
I ran: The rustc version was upgraded to 1.32.0
This solved the issue. |
@gabridome tried right now, it still doesn't work for me if edition is specified in |
@vn971 update to cargo-outdated 0.8.0, it was released a couple of weeks ago: https://crates.io/crates/cargo-outdated/0.8.0 |
Yes. In my case it worked. |
@dwijnand @gabridome it works for me as well now, thanks! The trick was indeed to update
|
caused by: editions are unstable
on Rust Edition 2018 RC1
I'm trying Rust Edition 2018 RC1 on my project and part of it was removing
cargo-features = ["edition"]
line. Most tools works correctly, but bothcargo-outdated
and my own project that usescargo
as a library stopped working and print:or similar when opening workspace:
It looks like for whatever reason they didn't get the memo that
cargo-features = ["edition"]
is not required anymore.It's a bit surprising since
cargo
on beta channel works just fine. Do I have to configure something in https://docs.rs/cargo/0.30.0/cargo/util/config/struct.Config.html ?The text was updated successfully, but these errors were encountered: