-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Nightly 2022-03-30 ICE: Collection VecMap(...) should have just one matching element #95538
Comments
Bisected: searched nightlies: from nightly-2022-03-29 to nightly-2022-03-31 bisected with cargo-bisect-rustc v0.6.1Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc |
Huh how did we miss this on crater? Either way, I know how to fix this. Maybe i'll even get it in before the beta cutoff. But even if not, the fix will be small and easily backported |
I ran into the compilation error testing against the |
The nightly rust compiler is currently unable to compile the version of fatfs we are using in xtask. Rust bug: rust-lang/rust#95538. But we don't need to use nightly to compile xtask. In the CI, install both stable and nightly toolchains. The stable toolchain will be used by default, and xtask already knows to insert `+nightly` when building uefi-rs, so there's no need to set `override: true` for the nightly toolchain anymore. Fixes #397
The nightly rust compiler is currently unable to compile the version of fatfs we are using in xtask. Rust bug: rust-lang/rust#95538. But we don't need to use nightly to compile xtask. In the CI, install both stable and nightly toolchains. The stable toolchain will be used by default, and xtask already knows to insert `+nightly` when building uefi-rs, so there's no need to set `override: true` for the nightly toolchain anymore. Fixes #397
The nightly rust compiler is currently unable to compile the version of fatfs we are using in xtask. Rust bug: rust-lang/rust#95538. But we don't need to use nightly to compile xtask. In the CI, install both stable and nightly toolchains. The stable toolchain will be used by default, and xtask already knows to insert `+nightly` when building uefi-rs, so there's no need to set `override: true` for the nightly toolchain anymore. Fixes #397
The nightly rust compiler is currently unable to compile the version of fatfs we are using in xtask. Rust bug: rust-lang/rust#95538. But we don't need to use nightly to compile xtask. In the CI, install both stable and nightly toolchains. The stable toolchain will be used by default, and xtask already knows to insert `+nightly` when building uefi-rs, so there's no need to set `override: true` for the nightly toolchain anymore. Fixes #397
The nightly rust compiler is currently unable to compile the version of fatfs we are using in xtask. Rust bug: rust-lang/rust#95538. But we don't need to use nightly to compile xtask. In the CI, install both stable and nightly toolchains. The stable toolchain will be used by default, and xtask already knows to insert `+nightly` when building uefi-rs, so there's no need to set `override: true` for the nightly toolchain anymore. Fixes #397
…piler-errors Check that all hidden types are the same and then deduplicate them. fixes rust-lang#95538 This used to trigger a sanity check. Now we accept that there may be multiple places where a hidden type is constrained and we merge all of these at the end. Ideally we'd merge eagerly, but that is a larger refactoring that I don't want to put into a backport
Assigning priority as discussed in the Zulip thread of the Prioritization Working Group. @rustbot label -I-prioritize +P-medium |
Still in beta, leaving open until we backport the PR |
Backported in #96367 |
Code
I ran into this error when compiling the fatfs crate with nightly. I reduced the example down to this, no external deps needed:
Playground link
Meta
rustc --version --verbose
:Compiles without errors on current stable/beta.
Error output
Backtrace
The text was updated successfully, but these errors were encountered: