-
Notifications
You must be signed in to change notification settings - Fork 13.3k
diagnostic_namespace
was not listed in declare_features
ICE
#122446
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
Comments
Here is the full ICE output: |
Turns out I was missing This wasn't a fix, the behavior still happened. |
Does this specifically only happen with clippy, or does this ICE also happen with a regular |
|
Moving to rust-lang/rust in that case, since it sounds like fixing this requires changes in the compiler and we can't do much about that on the clippy side |
From what I can tell, MCVE is #![deny(unknown_or_malformed_diagnostic_attributes)] or, alternatively, #![feature(diagnostic_namespace)]
#![deny(unknown_or_malformed_diagnostic_attributes)] |
searched nightlies: from nightly-2024-01-01 to nightly-2024-03-12 bisected with cargo-bisect-rustc v0.6.8Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc -vv --preserve --start=2024-01-01 --end=2024-03-12 --access=github --regress ice |
I filled #122482 to address this |
…rors Ungate the `UNKNOWN_OR_MALFORMED_DIAGNOSTIC_ATTRIBUTES` lint This was missed during stablisation of the `#[diagnostic]` attribute namespace. Fixes rust-lang#122446
Rollup merge of rust-lang#122482 - weiznich:fix/122446, r=compiler-errors Ungate the `UNKNOWN_OR_MALFORMED_DIAGNOSTIC_ATTRIBUTES` lint This was missed during stablisation of the `#[diagnostic]` attribute namespace. Fixes rust-lang#122446
Summary
When compiling my
unstable
feature anddiagnostic_namespace
is included I got the attached ICE.The following is the unstable configuration
https://github.com/rustyhorde/pud is the repository this occurs on. I will get a minimal verifiable example setup shortly.
Version
Error output
Backtrace
The text was updated successfully, but these errors were encountered: