rust/tests/ui/borrowck/issue-81899.stderr

error[E0080]: evaluation of constant value failed
  --> $DIR/issue-81899.rs:11:5
   |
LL |     panic!()
   |     ^^^^^^^^ the evaluated program panicked at 'explicit panic', $DIR/issue-81899.rs:11:5
   |
note: inside `f::<{closure@$DIR/issue-81899.rs:4:31: 4:34}>`
  --> $DIR/issue-81899.rs:11:5
   |
LL |     panic!()
   |     ^^^^^^^^
note: inside `_CONST`
  --> $DIR/issue-81899.rs:4:24
   |
LL | const _CONST: &[u8] = &f(&[], |_| {});
   |                        ^^^^^^^^^^^^^^
   = note: this error originates in the macro `$crate::panic::panic_2015` which comes from the expansion of the macro `panic` (in Nightly builds, run with -Z macro-backtrace for more info)

note: erroneous constant encountered
  --> $DIR/issue-81899.rs:4:23
   |
LL | const _CONST: &[u8] = &f(&[], |_| {});
   |                       ^^^^^^^^^^^^^^^

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0080`.
Add regression test for #81899 2022-05-27 11:32:15 -05:00			`error[E0080]: evaluation of constant value failed`
make const_err a hard error 2022-09-21 06:05:20 -05:00			`--> $DIR/issue-81899.rs:11:5`
Add regression test for #81899 2022-05-27 11:32:15 -05:00			`\|`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`LL \| panic!()`
			`\| ^^^^^^^^ the evaluated program panicked at 'explicit panic', $DIR/issue-81899.rs:11:5`
			`\|`
adjust how closure/generator types and rvalues are printed 2023-09-09 01:36:50 -05:00			note: inside `f::<{closure@$DIR/issue-81899.rs:4:31: 4:34}>`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`--> $DIR/issue-81899.rs:11:5`
			`\|`
Add regression test for #81899 2022-05-27 11:32:15 -05:00			`LL \| panic!()`
			`\| ^^^^^^^^`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			note: inside `_CONST`
			`--> $DIR/issue-81899.rs:4:24`
Add regression test for #81899 2022-05-27 11:32:15 -05:00			`\|`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`LL \| const _CONST: &[u8] = &f(&[], \|_\| {});`
			`\| ^^^^^^^^^^^^^^`
Mention first and last macro in backtrace 2022-06-20 21:25:52 -05:00			= note: this error originates in the macro `$crate::panic::panic_2015` which comes from the expansion of the macro `panic` (in Nightly builds, run with -Z macro-backtrace for more info)
Add regression test for #81899 2022-05-27 11:32:15 -05:00
don't point at const usage site for resolution-time errors also share the code that emits the actual error 2023-09-11 16:09:11 -05:00			`note: erroneous constant encountered`
implement valtrees as the type-system representation for constant values 2022-02-16 03:56:01 -06:00			`--> $DIR/issue-81899.rs:4:23`
			`\|`
			`LL \| const _CONST: &[u8] = &f(&[], \|_\| {});`
cleanup and dedupe CTFE and Miri error reporting 2022-11-15 05:06:20 -06:00			`\| ^^^^^^^^^^^^^^^`
implement valtrees as the type-system representation for constant values 2022-02-16 03:56:01 -06:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Add regression test for #81899 2022-05-27 11:32:15 -05:00
			For more information about this error, try `rustc --explain E0080`.