rust/tests/ui/panics/fmt-panic.rs

//@ run-fail
//@ error-pattern:meh
//@ ignore-emscripten no processes

fn main() {
    let str_var: String = "meh".to_string();
    panic!("{}", str_var);
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-fail`
			`//@ error-pattern:meh`
			`//@ ignore-emscripten no processes`
Manipulate contexts correctly in trans_fail_expr This fixes Issue #617 2011-07-03 09:38:11 +00:00
test: Remove all uses of `~str` from the test suite. 2014-05-13 00:56:43 +00:00			`fn main() {`
std: Rename strbuf operations to string [breaking-change] 2014-05-25 10:17:19 +00:00			`let str_var: String = "meh".to_string();`
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			`panic!("{}", str_var);`
test: Remove all uses of `~str` from the test suite. 2014-05-13 00:56:43 +00:00			`}`