rust/tests/ui/consts/const-eval/ub-slice-get-unchecked.stderr

error[E0015]: cannot call non-const fn `core::slice::<impl [()]>::get_unchecked::<std::ops::Range<usize>>` in constants
  --> $DIR/ub-slice-get-unchecked.rs:7:29
   |
LL | const B: &[()] = unsafe { A.get_unchecked(3..1) };
   |                             ^^^^^^^^^^^^^^^^^^^
   |
   = note: calls in constants are limited to constant functions, tuple structs and tuple variants

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0015`.
fix library and rustdoc tests 2023-04-16 06:12:37 -05:00			error[E0015]: cannot call non-const fn `core::slice::<impl [()]>::get_unchecked::<std::ops::Range<usize>>` in constants
remove const_slice_index annotations, it never had a feature gate anyway 2024-09-08 01:54:01 -05:00			`--> $DIR/ub-slice-get-unchecked.rs:7:29`
Use `nuw` when calculating slice lengths from `Range`s An `assume` would definitely not be worth it, but since the flag is almost free we might as well tell LLVM this, especially on `_unchecked` calls where there's no obvious way for it to deduce it. (Today neither safe nor unsafe indexing gets it: <https://rust.godbolt.org/z/G1jYT548s>) 2023-03-04 21:10:36 -06:00			`\|`
			`LL \| const B: &[()] = unsafe { A.get_unchecked(3..1) };`
fix library and rustdoc tests 2023-04-16 06:12:37 -05:00			`\| ^^^^^^^^^^^^^^^^^^^`
			`\|`
			`= note: calls in constants are limited to constant functions, tuple structs and tuple variants`
Use `nuw` when calculating slice lengths from `Range`s An `assume` would definitely not be worth it, but since the flag is almost free we might as well tell LLVM this, especially on `_unchecked` calls where there's no obvious way for it to deduce it. (Today neither safe nor unsafe indexing gets it: <https://rust.godbolt.org/z/G1jYT548s>) 2023-03-04 21:10:36 -06:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Use `nuw` when calculating slice lengths from `Range`s An `assume` would definitely not be worth it, but since the flag is almost free we might as well tell LLVM this, especially on `_unchecked` calls where there's no obvious way for it to deduce it. (Today neither safe nor unsafe indexing gets it: <https://rust.godbolt.org/z/G1jYT548s>) 2023-03-04 21:10:36 -06:00
fix library and rustdoc tests 2023-04-16 06:12:37 -05:00			For more information about this error, try `rustc --explain E0015`.