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

Why must this crate compile with nightly? #73

Closed
Nicholas-Baron opened this issue Jul 20, 2020 · 2 comments
Closed

Why must this crate compile with nightly? #73

Nicholas-Baron opened this issue Jul 20, 2020 · 2 comments
Labels
question Further information is requested

Comments

@Nicholas-Baron
Copy link
Contributor

I find it strange that a crate can be installed with stable, but must use nightly to run.

Trying to compile with stable gives the following error

the option Z is only accepted on the nightly compiler

Has the source of this error been tracked down? I do not see anything in this repository explicitly so it must be in one of the dependencies.

@qryxip
Copy link
Collaborator

qryxip commented Jul 20, 2020

That message comes from rustc.

$ rustc +stable -Z aaaaaaaaaa /dev/null
error: the option `Z` is only accepted on the nightly compiler

The reason is because cargo-udeps relies on the -Z save-analysis option, which is only available on nightly. So cargo-udeps itself does not need to be compiled with nightly toolchains.

cmd.arg("-Z").arg("save-analysis");

@est31
Copy link
Owner

est31 commented Jul 20, 2020

Yeah you can switch between save-analysis and binary-depinfo backends but both currently require nightly. save-analysis will likely be removed eventually but binary-depinfo might get stabilized. Maybe a backend based on the unused dependency warning can be added, that one would work on stable, cc #70.

@est31 est31 added the question Further information is requested label Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants