os-rust/tests/ui/conditional-compilation/cfg-in-crate-1.stderr

error[E0601]: `main` function not found in crate `cfg_in_crate_1`
  --> $DIR/cfg-in-crate-1.rs:3:13
   |
LL | #![cfg(bar)]
   |             ^ consider adding a `main` function to `$DIR/cfg-in-crate-1.rs`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0601`.
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			error[E0601]: `main` function not found in crate `cfg_in_crate_1`
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-21 00:15:39 +00:00			`--> $DIR/cfg-in-crate-1.rs:3:13`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02: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 13:06:49 -04:00			`LL \| #![cfg(bar)]`
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-21 00:15:39 +00:00			\| ^ consider adding a `main` function to `$DIR/cfg-in-crate-1.rs`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0601`.