-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Error running cargo fix
#5775
Comments
Thanks for the report! Would it be possible to poke around the crate you're seeing these errors from? Additionally, does this happen if you disable the |
No problem. Thanks for all the great work on my favorite programming language! The problem does not occur if I disable that lint group. I have emailed you at your GitHub profile email address, as I'm happy to share some code with you but do not want to post it publicly. |
Fix a formatting of a cargo fix message Something I saw in the report of #5775
Ok thanks so much for the info! I've reduced this down to two separate issues (both with lints in rustc)
I'm gonna close this in favor of them, thanks again for taking the time to report this! |
I tried this:
cargo +nightly fix --prepare-for 2018 --all-targets --all-features --allow-dirty
I expected to see this happen: for the
cargo fix
utility to fix all my code and prepare me for the wonderful future of Rust 2018.Instead, this happened: I got the following output (pasting the extremely long output of the command, as requested by the compiler message):
I'm using cargo 1.29.0-nightly (506eea7 2018-07-17)
The text was updated successfully, but these errors were encountered: