rust/src/test/ui/consts/const-eval/const_panic.stderr

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:7:15
   |
LL | const Z: () = std::panic!("cheese");
   |               ^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'cheese', $DIR/const_panic.rs:7:15
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:10:16
   |
LL | const Z2: () = std::panic!();
   |                ^^^^^^^^^^^^^ the evaluated program panicked at 'explicit panic', $DIR/const_panic.rs:10:16
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:13:15
   |
LL | const Y: () = std::unreachable!();
   |               ^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'internal error: entered unreachable code', $DIR/const_panic.rs:13:15
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:16:15
   |
LL | const X: () = std::unimplemented!();
   |               ^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'not implemented', $DIR/const_panic.rs:16:15
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:19:15
   |
LL | const W: () = std::panic!(MSG);
   |               ^^^^^^^^^^^^^^^^ the evaluated program panicked at 'hello', $DIR/const_panic.rs:19:15
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:22:16
   |
LL | const W2: () = std::panic!("{}", MSG);
   |                ^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'hello', $DIR/const_panic.rs:22:16
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:25:20
   |
LL | const Z_CORE: () = core::panic!("cheese");
   |                    ^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'cheese', $DIR/const_panic.rs:25:20
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:28:21
   |
LL | const Z2_CORE: () = core::panic!();
   |                     ^^^^^^^^^^^^^^ the evaluated program panicked at 'explicit panic', $DIR/const_panic.rs:28:21
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:31:20
   |
LL | const Y_CORE: () = core::unreachable!();
   |                    ^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'internal error: entered unreachable code', $DIR/const_panic.rs:31:20
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:34:20
   |
LL | const X_CORE: () = core::unimplemented!();
   |                    ^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'not implemented', $DIR/const_panic.rs:34:20
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:37:20
   |
LL | const W_CORE: () = core::panic!(MSG);
   |                    ^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'hello', $DIR/const_panic.rs:37:20
   |
   = note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_panic.rs:40:21
   |
LL | const W2_CORE: () = core::panic!("{}", MSG);
   |                     ^^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'hello', $DIR/const_panic.rs:40:21
   |
   = 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 12 previous errors

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`
Allow/fix non_fmt_panic in tests. 2021-02-01 23:40:17 +00:00			`--> $DIR/const_panic.rs:7:15`
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +00:00			`\|`
we can test std and core panic macros together 2020-10-18 12:34:30 +00:00			`LL \| const Z: () = std::panic!("cheese");`
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			`\| ^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'cheese', $DIR/const_panic.rs:7:15`
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +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)
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +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			`error[E0080]: evaluation of constant value failed`
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			`--> $DIR/const_panic.rs:10:16`
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +00:00			`\|`
we can test std and core panic macros together 2020-10-18 12:34:30 +00:00			`LL \| const Z2: () = std::panic!();`
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			`\| ^^^^^^^^^^^^^ the evaluated program panicked at 'explicit panic', $DIR/const_panic.rs:10:16`
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +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)
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +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			`error[E0080]: evaluation of constant value failed`
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			`--> $DIR/const_panic.rs:13:15`
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +00:00			`\|`
we can test std and core panic macros together 2020-10-18 12:34:30 +00:00			`LL \| const Y: () = std::unreachable!();`
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			`\| ^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'internal error: entered unreachable code', $DIR/const_panic.rs:13:15`
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +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)
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +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			`error[E0080]: evaluation of constant value failed`
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			`--> $DIR/const_panic.rs:16:15`
we can test std and core panic macros together 2020-10-18 12:34:30 +00:00			`\|`
			`LL \| const X: () = std::unimplemented!();`
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			`\| ^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'not implemented', $DIR/const_panic.rs:16:15`
we can test std and core panic macros together 2020-10-18 12:34:30 +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)
we can test std and core panic macros together 2020-10-18 12:34:30 +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			`error[E0080]: evaluation of constant value failed`
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			`--> $DIR/const_panic.rs:19:15`
Add test for const panic!(CONST). 2020-10-18 13:02:42 +00:00			`\|`
			`LL \| const W: () = std::panic!(MSG);`
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			`\| ^^^^^^^^^^^^^^^^ the evaluated program panicked at 'hello', $DIR/const_panic.rs:19:15`
Add test for const panic!(CONST). 2020-10-18 13:02:42 +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)
Add test for const panic!(CONST). 2020-10-18 13:02:42 +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			`error[E0080]: evaluation of constant value failed`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`--> $DIR/const_panic.rs:22:16`
			`\|`
			`LL \| const W2: () = std::panic!("{}", MSG);`
			`\| ^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'hello', $DIR/const_panic.rs:22:16`
			`\|`
			= note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

			`error[E0080]: evaluation of constant value failed`
			`--> $DIR/const_panic.rs:25:20`
we can test std and core panic macros together 2020-10-18 12:34:30 +00:00			`\|`
			`LL \| const Z_CORE: () = core::panic!("cheese");`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`\| ^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'cheese', $DIR/const_panic.rs:25:20`
we can test std and core panic macros together 2020-10-18 12:34:30 +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)
we can test std and core panic macros together 2020-10-18 12:34:30 +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			`error[E0080]: evaluation of constant value failed`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`--> $DIR/const_panic.rs:28:21`
we can test std and core panic macros together 2020-10-18 12:34:30 +00:00			`\|`
			`LL \| const Z2_CORE: () = core::panic!();`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`\| ^^^^^^^^^^^^^^ the evaluated program panicked at 'explicit panic', $DIR/const_panic.rs:28:21`
we can test std and core panic macros together 2020-10-18 12:34:30 +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)
we can test std and core panic macros together 2020-10-18 12:34:30 +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			`error[E0080]: evaluation of constant value failed`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`--> $DIR/const_panic.rs:31:20`
we can test std and core panic macros together 2020-10-18 12:34:30 +00:00			`\|`
			`LL \| const Y_CORE: () = core::unreachable!();`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`\| ^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'internal error: entered unreachable code', $DIR/const_panic.rs:31:20`
we can test std and core panic macros together 2020-10-18 12:34:30 +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)
we can test std and core panic macros together 2020-10-18 12:34:30 +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			`error[E0080]: evaluation of constant value failed`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`--> $DIR/const_panic.rs:34:20`
we can test std and core panic macros together 2020-10-18 12:34:30 +00:00			`\|`
			`LL \| const X_CORE: () = core::unimplemented!();`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`\| ^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'not implemented', $DIR/const_panic.rs:34:20`
Add test for const panic!(CONST). 2020-10-18 13:02:42 +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)
Add test for const panic!(CONST). 2020-10-18 13:02:42 +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			`error[E0080]: evaluation of constant value failed`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`--> $DIR/const_panic.rs:37:20`
Add test for const panic!(CONST). 2020-10-18 13:02:42 +00:00			`\|`
			`LL \| const W_CORE: () = core::panic!(MSG);`
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`\| ^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'hello', $DIR/const_panic.rs:37:20`
			`\|`
			= note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)

			`error[E0080]: evaluation of constant value failed`
			`--> $DIR/const_panic.rs:40:21`
			`\|`
			`LL \| const W2_CORE: () = core::panic!("{}", MSG);`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'hello', $DIR/const_panic.rs:40:21`
we can test std and core panic macros together 2020-10-18 12:34:30 +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)
we can test std and core panic macros together 2020-10-18 12:34:30 +00:00
Allow `panic!("{}", computed_str)` in const fn. 2021-09-14 18:14:37 +00:00			`error: aborting due to 12 previous errors`
Allow panicking with string literal messages inside constants 2018-08-13 11:48:47 +00:00
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`.