rust/tests/ui/simd/const-err-trumps-simd-err.stderr

error[E0080]: evaluation panicked: assertion failed: LANE < 4
  --> $DIR/const-err-trumps-simd-err.rs:17:13
   |
LL |     const { assert!(LANE < 4); } // the error should be here...
   |             ^^^^^^^^^^^^^^^^^ evaluation of `get_elem::<4>::{constant#0}` failed here

note: erroneous constant encountered
  --> $DIR/const-err-trumps-simd-err.rs:17:5
   |
LL |     const { assert!(LANE < 4); } // the error should be here...
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

note: the above error was encountered while instantiating `fn get_elem::<4>`
  --> $DIR/const-err-trumps-simd-err.rs:23:5
   |
LL |     get_elem::<4>(int8x4_t([0, 0, 0, 0]));
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0080`.
Use the informative error as the main const eval error message 2025-05-28 10:29:08 +00:00			`error[E0080]: evaluation panicked: assertion failed: LANE < 4`
Revert "Rollup merge of #122661 - estebank:assert-macro-span, r=petrochenkov" This reverts commit 1eeb8e8b151d1da7daa73837a25dc5f7a1a7fa28, reversing changes made to 324bf2b9fd8bf9661e7045c8a93f5ff0ec1a8ca5. Unfortunately the assert desugaring change is not backwards compatible, see RUST-145770. Code such as ```rust #[derive(Debug)] struct F { data: bool } impl std::ops::Not for F { type Output = bool; fn not(self) -> Self::Output { !self.data } } fn main() { let f = F { data: true }; assert!(f); } ``` would be broken by the assert desugaring change. We may need to land the change over an edition boundary, or limit the editions that the desugaring change impacts. 2025-09-11 09:00:01 +08:00			`--> $DIR/const-err-trumps-simd-err.rs:17:13`
add test ensuring simd codegen checks don't run when a static assertion failed 2024-03-10 12:28:23 +01:00			`\|`
			`LL \| const { assert!(LANE < 4); } // the error should be here...`
Revert "Rollup merge of #122661 - estebank:assert-macro-span, r=petrochenkov" This reverts commit 1eeb8e8b151d1da7daa73837a25dc5f7a1a7fa28, reversing changes made to 324bf2b9fd8bf9661e7045c8a93f5ff0ec1a8ca5. Unfortunately the assert desugaring change is not backwards compatible, see RUST-145770. Code such as ```rust #[derive(Debug)] struct F { data: bool } impl std::ops::Not for F { type Output = bool; fn not(self) -> Self::Output { !self.data } } fn main() { let f = F { data: true }; assert!(f); } ``` would be broken by the assert desugaring change. We may need to land the change over an edition boundary, or limit the editions that the desugaring change impacts. 2025-09-11 09:00:01 +08:00			\| ^^^^^^^^^^^^^^^^^ evaluation of `get_elem::<4>::{constant#0}` failed here
add test ensuring simd codegen checks don't run when a static assertion failed 2024-03-10 12:28:23 +01:00
preserve span when evaluating mir::ConstOperand 2024-03-14 08:09:21 +01:00			`note: erroneous constant encountered`
stabilize gai 2025-06-11 15:30:15 +01:00			`--> $DIR/const-err-trumps-simd-err.rs:17:5`
preserve span when evaluating mir::ConstOperand 2024-03-14 08:09:21 +01:00			`\|`
			`LL \| const { assert!(LANE < 4); } // the error should be here...`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^`

add test ensuring simd codegen checks don't run when a static assertion failed 2024-03-10 12:28:23 +01:00			note: the above error was encountered while instantiating `fn get_elem::<4>`
stabilize gai 2025-06-11 15:30:15 +01:00			`--> $DIR/const-err-trumps-simd-err.rs:23:5`
add test ensuring simd codegen checks don't run when a static assertion failed 2024-03-10 12:28:23 +01:00			`\|`
Ban non-array SIMD 2024-08-22 01:28:20 -07:00			`LL \| get_elem::<4>(int8x4_t([0, 0, 0, 0]));`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
add test ensuring simd codegen checks don't run when a static assertion failed 2024-03-10 12:28:23 +01:00
			`error: aborting due to 1 previous error`

			For more information about this error, try `rustc --explain E0080`.