rust/tests/ui/array-slice-vec/vec-overrun.rs

// run-fail
// error-pattern:index out of bounds: the len is 1 but the index is 2
// ignore-emscripten no processes

fn main() {
    let v: Vec<isize> = vec![10];
    let x: usize = 0;
    assert_eq!(v[x], 10);
    // Bounds-check panic.

    assert_eq!(v[x + 2], 20);
}
Move tests from `test/run-fail` to UI 2020-04-16 01:50:32 -05:00			`// run-fail`
When a vec/str bounds check fails, include the bad index and the length of the str/vec in the fail message. 2012-09-29 06:34:11 -05:00			`// error-pattern:index out of bounds: the len is 1 but the index is 2`
Skip tests on emscripten 2020-05-07 10:39:02 -05:00			`// ignore-emscripten no processes`
test: Make manual changes to deal with the fallout from removal of `~[T]` in test, libgetopts, compiletest, librustdoc, and libnum. 2014-03-05 17:28:08 -06:00
Populate tree. 2010-06-23 23:03:09 -05:00			`fn main() {`
run rustfmt on test/run-fail folder 2016-05-26 21:39:36 -05:00			`let v: Vec<isize> = vec![10];`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 19:06:52 -05:00			`let x: usize = 0;`
Remove a large amount of deprecated functionality Spring cleaning is here! In the Fall! This commit removes quite a large amount of deprecated functionality from the standard libraries. I tried to ensure that only old deprecated functionality was removed. This is removing lots and lots of deprecated features, so this is a breaking change. Please consult the deprecation messages of the deleted code to see how to migrate code forward if it still needs migration. [breaking-change] 2014-10-15 01:05:01 -05:00			`assert_eq!(v[x], 10);`
Rename fail! to panic! https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . \| xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] 2014-10-09 14:17:22 -05:00			`// Bounds-check panic.`
Reformat source tree (minus a couple tests that are still grumpy). 2011-06-15 13:19:50 -05:00
Remove a large amount of deprecated functionality Spring cleaning is here! In the Fall! This commit removes quite a large amount of deprecated functionality from the standard libraries. I tried to ensure that only old deprecated functionality was removed. This is removing lots and lots of deprecated features, so this is a breaking change. Please consult the deprecation messages of the deleted code to see how to migrate code forward if it still needs migration. [breaking-change] 2014-10-15 01:05:01 -05:00			`assert_eq!(v[x + 2], 20);`
Port the tests to the typaram foo<T> syntax. 2011-08-10 11:27:22 -05:00			`}`