rust/tests/ui/str/str-overrun.rs

//@ run-fail
//@ error-pattern:index out of bounds: the len is 5 but the index is 5
//@ needs-subprocess

fn main() {
    let s: String = "hello".to_string();

    // Bounds-check panic.
    assert_eq!(s.as_bytes()[5], 0x0 as u8);
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-fail`
			`//@ error-pattern:index out of bounds: the len is 5 but the index is 5`
tests: use `needs-subprocess` instead of `ignore-{wasm32,emscripten,sgx}` 2025-01-23 08:36:54 +00:00			`//@ needs-subprocess`
Move tests from `test/run-fail` to UI 2020-04-16 06:50:32 +00:00
Populate tree. 2010-06-24 04:03:09 +00:00			`fn main() {`
std: Rename strbuf operations to string [breaking-change] 2014-05-25 10:17:19 +00:00			`let s: String = "hello".to_string();`
Populate tree. 2010-06-24 04:03:09 +00:00
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 19:17:22 +00:00			`// Bounds-check panic.`
rustc: Remove `&str` indexing from the language. Being able to index into the bytes of a string encourages poor UTF-8 hygiene. To get a view of `&[u8]` from either a `String` or `&str` slice, use the `as_bytes()` method. Closes #12710. [breaking-change] 2014-06-20 01:22:33 +00:00			`assert_eq!(s.as_bytes()[5], 0x0 as u8);`
Reformat This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[] 2011-08-19 22:16:48 +00:00			`}`