rust/tests/ui/extenv/extenv-not-defined-custom.stderr

error: my error message
  --> $DIR/extenv-not-defined-custom.rs:1:13
   |
LL | fn main() { env!("__HOPEFULLY_NOT_DEFINED__", "my error message"); }
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`error: my error message`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/extenv-not-defined-custom.rs:1:13`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| fn main() { env!("__HOPEFULLY_NOT_DEFINED__", "my error message"); }`
Bless tests 2021-10-14 13:28:28 -05:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
expand `env!` with def-site context 2020-05-26 19:45:30 -04:00			`\|`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 14:52:25 -05:00			= note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			`error: aborting due to previous error`