os-rust/tests/ui/issues/issue-3029.rs

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

#![allow(unreachable_code)]

fn main() {
    let mut x = Vec::new();
    let y = vec![3];
    panic!("so long");
    x.extend(y.into_iter());
}
Move tests from `test/run-fail` to UI 2020-04-16 15:50:32 +09:00			`//@ run-fail`
			`//@ error-pattern:so long`
Skip tests on emscripten 2020-05-08 00:39:02 +09:00			`//@ ignore-emscripten no processes`
Move tests from `test/run-fail` to UI 2020-04-16 15:50:32 +09:00
Use new attribute syntax in python files in src/etc too (#13478) 2014-04-14 21:00:31 +05:30			`#![allow(unreachable_code)]`
Fix warnings it tests 2013-08-17 08:37:42 -07:00
testsuite: Un-xfail test for #3029 and move to run-fail 2013-01-20 20:33:54 -08:00			`fn main() {`
test: Automatically remove all `~[T]` from tests. 2014-03-05 14:02:44 -08:00			`let mut x = Vec::new();`
run rustfmt on test/run-fail folder 2016-05-27 08:09:36 +05:30			`let y = vec![3];`
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 15:17:22 -04:00			`panic!("so long");`
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-14 23:05:01 -07:00			`x.extend(y.into_iter());`
Add xfailed test case for #3029 2012-07-26 14:51:10 -07:00			`}`