rust/tests/ui/attributes/crate-name-mismatch.rs

//! Checks error handling for mismatched `--crate-name` and `#![crate_name]` values.

//@ compile-flags: --crate-name foo

#![crate_name = "bar"]
//~^ ERROR: `--crate-name` and `#[crate_name]` are required to match, but `foo` != `bar`

fn main() {}
cleaned up some tests 2025-06-07 16:17:21 +05:00			//! Checks error handling for mismatched `--crate-name` and `#![crate_name]` values.

rustc: Mix extra-filename in temp outputs When invoking the compiler in parallel, the intermediate output of the object files and bytecode can stomp over one another if two crates with the same name are being compiled. The output file is already being disambiguated with `-C extra-filename`, so this commit alters the naming of the temporary files to also mix in the extra filename to ensure that file names don't clash. 2014-07-15 09:13:58 -07:00			`//@ compile-flags: --crate-name foo`
rustc: #[crate_name] and --crate-name must match Part of the original discussions around the `--crate-name` flag brought up that mass confusion can arise when the flag specifies a different name than is contained in the crate. The current primary use case of the `--crate-name` flag is through cargo and not requiring a `#[crate_name]` attribute, but if the `#[crate_name]` attribute is specified it will likely go awry when the two names deviate from one another. This commit requires that if both are provided they both match to prevent this confusion. 2014-07-15 09:13:40 -07:00
			`#![crate_name = "bar"]`
normalize use of backticks for compiler messages in librustc_codegen https://github.com/rust-lang/rust/issues/60532 2019-07-07 23:14:41 +02:00			//~^ ERROR: `--crate-name` and `#[crate_name]` are required to match, but `foo` != `bar`
rustc: #[crate_name] and --crate-name must match Part of the original discussions around the `--crate-name` flag brought up that mass confusion can arise when the flag specifies a different name than is contained in the crate. The current primary use case of the `--crate-name` flag is through cargo and not requiring a `#[crate_name]` attribute, but if the `#[crate_name]` attribute is specified it will likely go awry when the two names deviate from one another. This commit requires that if both are provided they both match to prevent this confusion. 2014-07-15 09:13:40 -07:00
			`fn main() {}`