rust/tests/ui/consts/const-unwrap.stderr

error[E0080]: evaluation of constant value failed
  --> $DIR/const-unwrap.rs:7:18
   |
LL | const BAR: i32 = Option::<i32>::None.unwrap();
   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'called `Option::unwrap()` on a `None` value', $DIR/const-unwrap.rs:7:38

error: aborting due to previous error

For more information about this error, try `rustc --explain E0080`.
Use better error message for hard errors in CTFE Currently the same message is used for hard errors and soft errors. This makes hard errors use a message that indicates the reality of the situation correctly, since usage of the constant is never allowed when there was a hard error evaluating it. 2021-06-15 18:16:10 -05:00			`error[E0080]: evaluation of constant value failed`
Use #[track_caller] in const panic diagnostics. It was already used for the message. This also uses it for the spans used for the error and backtrace. 2021-07-09 08:21:58 -05:00			`--> $DIR/const-unwrap.rs:7:18`
Test `Option::unwrap` in a const context 2020-07-30 14:32:20 -05:00			`\|`
			`LL \| const BAR: i32 = Option::<i32>::None.unwrap();`
Use #[track_caller] in const panic diagnostics. It was already used for the message. This also uses it for the spans used for the error and backtrace. 2021-07-09 08:21:58 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'called `Option::unwrap()` on a `None` value', $DIR/const-unwrap.rs:7:38
Test `Option::unwrap` in a const context 2020-07-30 14:32:20 -05:00
			`error: aborting due to previous error`

Emit a hard error when a panic occurs during const-eval Previous, a panic during const evaluation would go through the `const_err` lint. This PR ensures that such a panic always causes compilation to fail. 2021-05-25 20:54:59 -05:00			For more information about this error, try `rustc --explain E0080`.