rust/src/test/ui/array-slice-vec/bounds-check-no-overflow.rs

// run-fail
// error-pattern:index out of bounds

use std::usize;
use std::mem::size_of;

fn main() {
    let xs = [1, 2, 3];
    xs[usize::MAX / size_of::<isize>() + 1];
}
Move tests from `test/run-fail` to UI 2020-04-16 15:50:32 +09:00			`// run-fail`
core: Use primitive indexing in slice's Index/IndexMut [T]'s Index implementation is normally not used for indexing, instead the compiler supplied indexing is used. Use the compiler supplied version in Index/IndexMut. This removes an inconsistency: Compiler supplied bound check failures look like this: thread 'main' panicked at 'index out of bounds: the len is 3 but the index is 4' If you convince Rust to use the Index impl for slices, bounds check failure looks like this instead: thread 'main' panicked at 'assertion failed: index < self.len()' The latter is used if you for example use Index generically:: use std::ops::Index; fn foo<T: ?Sized>(x: &T) where T: Index<usize> { &x[4]; } foo(&[1, 2, 3][..]) 2016-09-13 20:51:39 +02:00			`// error-pattern:index out of bounds`
fix overflow on bounds checks Closes #9020 2013-10-14 23:25:33 -04:00
Remove int/uint from libstd/lib.rs 2015-02-27 01:43:55 +01:00			`use std::usize;`
std: Move size/align functions to std::mem. #2240 2013-10-16 18:34:01 -07:00			`use std::mem::size_of;`
fix overflow on bounds checks Closes #9020 2013-10-14 23:25:33 -04:00
			`fn main() {`
Remove all `i` suffixes 2015-01-25 22:05:03 +01:00			`let xs = [1, 2, 3];`
Remove int/uint from libstd/lib.rs 2015-02-27 01:43:55 +01:00			`xs[usize::MAX / size_of::<isize>() + 1];`
fix overflow on bounds checks Closes #9020 2013-10-14 23:25:33 -04:00			`}`