rust/tests/ui/main-wrong-location.stderr

error[E0601]: `main` function not found in crate `main_wrong_location`
  --> $DIR/main-wrong-location.rs:5:2
   |
LL | }
   |  ^ the main function must be defined at the crate level (in `$DIR/main-wrong-location.rs`)
   |
note: here is a function named `main`
  --> $DIR/main-wrong-location.rs:4:5
   |
LL |     fn main() { }
   |     ^^^^^^^^^
   = note: you have one or more functions named `main` not defined at the crate level
   = help: consider moving the `main` function definitions

error: aborting due to previous error

For more information about this error, try `rustc --explain E0601`.
Add backticks to `main` not found errors. 2018-03-13 13:22:43 -05:00			error[E0601]: `main` function not found in crate `main_wrong_location`
Do not point at whole file missing `fn main` Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be worse. This change will make it so that VSCode will not underline the whole file when `main` is missing, so other errors will be visible. 2022-01-20 18:15:39 -06:00			`--> $DIR/main-wrong-location.rs:5:2`
Update UI tests 2018-02-22 18:42:32 -06:00			`\|`
Do not point at whole file missing `fn main` Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be worse. This change will make it so that VSCode will not underline the whole file when `main` is missing, so other errors will be visible. 2022-01-20 18:15:39 -06:00			`LL \| }`
			\| ^ the main function must be defined at the crate level (in `$DIR/main-wrong-location.rs`)
Provide a span if main function is not present in crate Unfortunately, the diagnotic machinery does not cope well with an empty span which can happen if the crate is empty, in which case we merely set a spanless note. 2019-09-08 12:06:49 -05:00			`\|`
			note: here is a function named `main`
Do not point at whole file missing `fn main` Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be worse. This change will make it so that VSCode will not underline the whole file when `main` is missing, so other errors will be visible. 2022-01-20 18:15:39 -06:00			`--> $DIR/main-wrong-location.rs:4:5`
Update UI tests 2018-02-22 18:42:32 -06:00			`\|`
			`LL \| fn main() { }`
optimize find_item to fetch Item only when needed Signed-off-by: Miguel Guarniz <mi9uel9@gmail.com> 2022-05-03 16:58:19 -05:00			`\| ^^^^^^^^^`
Provide a span if main function is not present in crate Unfortunately, the diagnotic machinery does not cope well with an empty span which can happen if the crate is empty, in which case we merely set a spanless note. 2019-09-08 12:06:49 -05:00			= note: you have one or more functions named `main` not defined at the crate level
Remove #[main] attribute. 2021-04-08 08:37:38 -05:00			= help: consider moving the `main` function definitions
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00
			`error: aborting due to previous error`

update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0601`.