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

error: environment variable `CARGO__HOPEFULLY_NOT_DEFINED__` not defined at compile time
  --> $DIR/extenv-not-defined-default.rs:2:5
   |
LL |     env!("CARGO__HOPEFULLY_NOT_DEFINED__");
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: Cargo sets build script variables at run time. Use `std::env::var("CARGO__HOPEFULLY_NOT_DEFINED__")` instead
   = 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
Explain compile-time vs run-time difference in env!() error message 2023-02-28 10:20:43 -06:00			error: environment variable `CARGO__HOPEFULLY_NOT_DEFINED__` not defined at compile time
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/extenv-not-defined-default.rs:2:5`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Explain compile-time vs run-time difference in env!() error message 2023-02-28 10:20:43 -06:00			`LL \| env!("CARGO__HOPEFULLY_NOT_DEFINED__");`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
expand `env!` with def-site context 2020-05-26 18:45:30 -05:00			`\|`
Explain compile-time vs run-time difference in env!() error message 2023-02-28 10:20:43 -06:00			= help: Cargo sets build script variables at run time. Use `std::env::var("CARGO__HOPEFULLY_NOT_DEFINED__")` instead
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 13:52:25 -06: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 07:28:26 -05:00
			`error: aborting due to previous error`