rust/tests/ui/parser/mod_file_not_exist.rs

mod not_a_real_file; //~ ERROR file not found for module `not_a_real_file`
//~^ HELP to create the module `not_a_real_file`, create file

fn main() {
    assert_eq!(mod_file_aux::bar(), 10);
    //~^ ERROR failed to resolve: use of unresolved module or unlinked crate `mod_file_aux`
    //~| HELP you might be missing a crate named `mod_file_aux`
}
syntax: Bless mod.rs. #4116 When loading a module the parser will look for either foo.rs or foo/mod.rs and generate an error when both are found. 2013-07-19 19:11:30 -07:00			mod not_a_real_file; //~ ERROR file not found for module `not_a_real_file`
--bless windows test 2020-03-17 04:39:22 +01:00			//~^ HELP to create the module `not_a_real_file`, create file
Report errors better when failing to open files for sub-parsers 2012-11-18 14:14:40 -08:00
			`fn main() {`
Use assert_eq! rather than assert! where possible 2013-05-18 22:02:45 -04:00			`assert_eq!(mod_file_aux::bar(), 10);`
Reword "crate not found" resolve message ``` error[E0432]: unresolved import `some_novel_crate` --> file.rs:1:5 \| 1 \| use some_novel_crate::Type; \| ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `some_novel_crate` ``` On resolve errors where there might be a missing crate, mention `cargo add foo`: ``` error[E0433]: failed to resolve: use of unresolved module or unlinked crate `nope` --> $DIR/conflicting-impl-with-err.rs:4:11 \| LL \| impl From<nope::Thing> for Error { \| ^^^^ use of unresolved module or unlinked crate `nope` \| = help: if you wanted to use a crate named `nope`, use `cargo add nope` to add it to your `Cargo.toml` ``` 2024-11-18 03:42:16 +00:00			//~^ ERROR failed to resolve: use of unresolved module or unlinked crate `mod_file_aux`
			//~\| HELP you might be missing a crate named `mod_file_aux`
librustc: Replace `impl Type : Trait` with `impl Trait for Type`. rs=implflipping 2013-02-14 11:47:00 -08:00			`}`