rust/tests/ui/consts/const-eval/const_fn_ptr_fail2.stderr

error[E0080]: evaluation of constant value failed
  --> $DIR/const_fn_ptr_fail2.rs:9:5
   |
LL |     x(y)
   |     ^^^^ calling non-const function `double`
   |
note: inside `bar`
  --> $DIR/const_fn_ptr_fail2.rs:9:5
   |
LL |     x(y)
   |     ^^^^
note: inside `Y`
  --> $DIR/const_fn_ptr_fail2.rs:14:18
   |
LL | const Y: usize = bar(X, 2); // FIXME: should fail to typeck someday
   |                  ^^^^^^^^^

error[E0080]: evaluation of constant value failed
  --> $DIR/const_fn_ptr_fail2.rs:9:5
   |
LL |     x(y)
   |     ^^^^ calling non-const function `double`
   |
note: inside `bar`
  --> $DIR/const_fn_ptr_fail2.rs:9:5
   |
LL |     x(y)
   |     ^^^^
note: inside `Z`
  --> $DIR/const_fn_ptr_fail2.rs:15:18
   |
LL | const Z: usize = bar(double, 2); // FIXME: should fail to typeck someday
   |                  ^^^^^^^^^^^^^^

warning: skipping const checks
   |
help: skipping check that does not even have a feature gate
  --> $DIR/const_fn_ptr_fail2.rs:9:5
   |
LL |     x(y)
   |     ^^^^

error: aborting due to 2 previous errors; 1 warning emitted

For more information about this error, try `rustc --explain E0080`.
clean up some const error reporting around promoteds 2021-01-24 05:50:30 -06:00			`error[E0080]: evaluation of constant value failed`
make const_err a hard error 2022-09-21 06:05:20 -05:00			`--> $DIR/const_fn_ptr_fail2.rs:9:5`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -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 \| x(y)`
			\| ^^^^ calling non-const function `double`
			`\|`
			note: inside `bar`
			`--> $DIR/const_fn_ptr_fail2.rs:9:5`
			`\|`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00			`LL \| x(y)`
			`\| ^^^^`
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 `Y`
			`--> $DIR/const_fn_ptr_fail2.rs:14:18`
			`\|`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00			`LL \| const Y: usize = bar(X, 2); // FIXME: should fail to typeck someday`
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			`\| ^^^^^^^^^`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00
make const_err a hard error 2022-09-21 06:05:20 -05:00			`error[E0080]: evaluation of constant value failed`
			`--> $DIR/const_fn_ptr_fail2.rs:9:5`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -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 \| x(y)`
			\| ^^^^ calling non-const function `double`
			`\|`
			note: inside `bar`
			`--> $DIR/const_fn_ptr_fail2.rs:9:5`
			`\|`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00			`LL \| x(y)`
			`\| ^^^^`
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 `Z`
			`--> $DIR/const_fn_ptr_fail2.rs:15:18`
			`\|`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00			`LL \| const Z: usize = bar(double, 2); // FIXME: should fail to typeck someday`
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			`\| ^^^^^^^^^^^^^^`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00
make const_err a hard error 2022-09-21 06:05:20 -05:00			`warning: skipping const checks`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00			`\|`
make const_err a hard error 2022-09-21 06:05:20 -05:00			`help: skipping check that does not even have a feature gate`
			`--> $DIR/const_fn_ptr_fail2.rs:9:5`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00			`\|`
make const_err a hard error 2022-09-21 06:05:20 -05:00			`LL \| x(y)`
			`\| ^^^^`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00
make const_err a hard error 2022-09-21 06:05:20 -05:00			`error: aborting due to 2 previous errors; 1 warning emitted`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00
make const_err a hard error 2022-09-21 06:05:20 -05:00			For more information about this error, try `rustc --explain E0080`.