rust/src/test/ui/consts/const-unwrap.stderr

error[E0080]: evaluation of constant value failed
  --> $SRC_DIR/core/src/option.rs:LL:COL
   |
LL |             None => panic!("called `Option::unwrap()` on a `None` value"),
   |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                     |
   |                     the evaluated program panicked at 'called `Option::unwrap()` on a `None` value', $DIR/const-unwrap.rs:9:38
   |                     inside `Option::<i32>::unwrap` at $SRC_DIR/core/src/panic.rs:LL:COL
   | 
  ::: $DIR/const-unwrap.rs:9:18
   |
LL | const BAR: i32 = Option::<i32>::None.unwrap();
   |                  ---------------------------- inside `BAR` at $DIR/const-unwrap.rs:9:18
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

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 23:16:10 +00:00			`error[E0080]: evaluation of constant value failed`
Test `Option::unwrap` in a const context 2020-07-30 19:32:20 +00:00			`--> $SRC_DIR/core/src/option.rs:LL:COL`
			`\|`
			LL \| None => panic!("called `Option::unwrap()` on a `None` value"),
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
			`\| \|`
			\| the evaluated program panicked at 'called `Option::unwrap()` on a `None` value', $DIR/const-unwrap.rs:9:38
Implement new panic!() behaviour for Rust 2021. 2021-01-09 15:52:06 +00:00			\| inside `Option::<i32>::unwrap` at $SRC_DIR/core/src/panic.rs:LL:COL
Test `Option::unwrap` in a const context 2020-07-30 19:32:20 +00:00			`\|`
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 23:16:10 +00:00			`::: $DIR/const-unwrap.rs:9:18`
Test `Option::unwrap` in a const context 2020-07-30 19:32:20 +00:00			`\|`
			`LL \| const BAR: i32 = Option::<i32>::None.unwrap();`
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 23:16:10 +00:00			\| ---------------------------- inside `BAR` at $DIR/const-unwrap.rs:9:18
Test `Option::unwrap` in a const context 2020-07-30 19:32:20 +00: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 19:52:25 +00:00			= note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)
Test `Option::unwrap` in a const context 2020-07-30 19:32:20 +00: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-26 01:54:59 +00:00			For more information about this error, try `rustc --explain E0080`.