Closed ambaxter closed 5 years ago
I had the same issue on another code base (cargo fix
failed but didn't show any actual compiler errors.) If it'd be useful to share the code (or open a separate issue) please let me know.
Please do!
This is due to rust-lang/rust#54180.
According to the issue that shouldn't be a problem with the 2018 edition?
According to the issue that shouldn't be a problem with the 2018 edition?
Yea, I feel like that statement isn't quite correct. Using default binding modes is preferred in all editions, but AFAIK there are no lints for converting the old style (even with the idiom lints). Would you mind making a comment on the issue that it is affecting you on the 2018 edition? I'd fix it myself, but I don't know enough about compiler lints to know how to grow the span.
Oh, and just FYI, if you're confused that cargo didn't display the actual error, you can pass the --broken-code
option to cargo fix
to force it to leave the code in a broken state in which case you can manually inspect it and fix it.
updated
@ehuss yes, that was the problem. Thanks!
Oh, I meant leave a comment on rust-lang/rust#54180. This is an issue with rustc, and the more people that report something can sometimes help raise the priority. Someone who works on the compiler will need to fix it.
Done
Sounds like this was diagnosed (yay!) so I'm going to close this in favor of the upstream Rust bug
Problem cargo fix fails without any errors for the new 2018 edition
Steps
Notes
Output of
cargo version
: abaxter$ cargo version cargo 1.32.0-nightly (5e85ba14a 2018-12-02)OS: OS X 10.4.1