rust/tests/ui/consts/const-external-macro-const-err.stderr

error[E0080]: index out of bounds: the length is 1 but the index is 1
  --> $DIR/const-external-macro-const-err.rs:12:5
   |
LL |     static_assert!(2 + 2 == 5);
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^ evaluation of `main::_` failed here
   |
   = note: this error originates in the macro `static_assert` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0080`.
Use the informative error as the main const eval error message 2025-05-28 10:29:08 +00:00			`error[E0080]: index out of bounds: the length is 1 but the index is 1`
Add regression test for CONST_ERR lints in extern macros 2019-10-11 17:13:38 -04:00			`--> $DIR/const-external-macro-const-err.rs:12:5`
			`\|`
			`LL \| static_assert!(2 + 2 == 5);`
const-eval error: always say in which item the error occurred also adjust the wording a little so that we don't say "the error occurred here" for two different spans 2025-06-07 11:32:09 +02:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^ evaluation of `main::_` failed here
Add regression test for CONST_ERR lints in extern macros 2019-10-11 17:13:38 -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 `static_assert` (in Nightly builds, run with -Z macro-backtrace for more info)
Add regression test for CONST_ERR lints in extern macros 2019-10-11 17:13:38 -04:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Add regression test for CONST_ERR lints in extern macros 2019-10-11 17:13:38 -04:00
make const_err a hard error 2022-09-21 13:05:20 +02:00			For more information about this error, try `rustc --explain E0080`.