Rust errors / Names, paths and imports
Rust compiler error · checked with rustc 1.99.0
Rust error E0453: allow(non_snake_case) incompatible with previous forbid
What it meansA lint check attribute was overruled by a forbid directive set as an attribute on an enclosing scope, or on the command line with the -F option.
What rustc prints
error[E0453]: allow(non_snake_case) incompatible with previous forbid
--> main.rs:3:9
|
1 | #![forbid(non_snake_case)]
| -------------- `forbid` level set here
2 |
3 | #[allow(non_snake_case)]
| ^^^^^^^^^^^^^^ overruled by previous forbidReal output of rustc 1.99.0 compiling the official example below (2021 edition). Your names and line numbers will differ; the first line is the part to match.
The compiler team's explanation
A lint check attribute was overruled by a forbid directive set as an attribute on an enclosing scope, or on the command line with the -F option.
Example of erroneous code:
#![forbid(non_snake_case)]
#[allow(non_snake_case)]
fn main() {
// error: allow(non_snake_case) incompatible with previous forbid
let MyNumber = 2;
}
The forbid lint setting, like deny, turns the corresponding compiler warning into a hard error. Unlike deny, forbid prevents itself from being overridden by inner attributes.
If you're sure you want to override the lint check, you can change forbid to deny (or use -D instead of -F if the forbid setting was given as a command-line option) to allow the inner lint check attribute:
#![deny(non_snake_case)]
#[allow(non_snake_case)]
fn main() {
let MyNumber = 2; // ok!
}
Otherwise, edit the code to pass the lint check, and remove the overruled attribute:
#![forbid(non_snake_case)]
fn main() {
let my_number = 2;
}From rustc --explain E0453 (1.99.0), part of the Rust project, MIT or Apache-2.0. Official page.
Related errors
Up next
Often hit nextE0425: cannot find value in this scopeA related error from the same family.Read it next →Did this answer your question?