-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
"inconsistent resolution for an import" with Rust 2018 #56596
Comments
@Thinkofname Minimizing reproduction is not necessary, the whole crate causing the error would work too. |
The code is from a private project that isn't the easiest to build. I managed to reduce it down to a small-ish test case without all the dependencies though. |
Thanks! |
I ran into a similar ICE with the same message (but possibly unrelated) with the latest nightly:
Project triggering the ICE: https://github.com/ennis/inconsistent_import Output of
Steps to reproduce: |
The issue described in the comment above (#56596 (comment)) is fixed in #57160. |
Fixed in #57181 |
resolve: Fix an ICE in import validation Fixes ICE reported in the comment #56596 (comment)
resolve: Fix an ICE in import validation Fixes ICE reported in the comment #56596 (comment)
resolve: Fix another ICE in import validation Imports are allowed to have ambiguous resolutions as long as all of them have same `Def`. As it turned out, it's possible for different `Module`s to have same `Def` when `extern crate` items are involved. Fixes #56596
I was trying to use the 2018 edition with my game and after running cargo fix and then trying to cargo check the result I got the following panic. This only happens if
edition = "2018"
is set in myCargo.toml
, if its not set it compiles fine. I'm not sure where its crashing so I can't provide a test case yet.Rustc version:
rustc 1.31.0 (abe02cefd 2018-12-04)
Backtrace:
The text was updated successfully, but these errors were encountered: