rust/src/test/ui/process/tls-exit-status.rs

// run-fail
// error-pattern:nonzero
// exec-env:RUST_NEWRT=1
// ignore-cloudabi no std::env

use std::env;

fn main() {
    env::args();
    panic!("please have a nonzero exit status");
}
Move tests from `test/run-fail` to UI 2020-04-16 01:50:32 -05:00			`// run-fail`
Add tests for issues which can be closed Closes #5275, $4547 2013-07-19 21:01:46 -05:00			`// error-pattern:nonzero`
			`// exec-env:RUST_NEWRT=1`
Add 'ignore-cloudabi' to tests that don't and won't build on CloudABI. It looks like many of these tests are already disabled on emscripten, which also doesn't seem to support environment variables and subprocess spawning. Just add a similar tag for CloudABI. While there, sort some of the lists of operating systems alphabetically. 2018-01-02 07:11:41 -06:00			`// ignore-cloudabi no std::env`
Add tests for issues which can be closed Closes #5275, $4547 2013-07-19 21:01:46 -05:00
Replace some uses of deprecated os functions This commit mostly replaces some of the uses of os::args with env::args. 2015-02-16 08:04:02 -06:00			`use std::env;`
Add tests for issues which can be closed Closes #5275, $4547 2013-07-19 21:01:46 -05:00
			`fn main() {`
Replace some uses of deprecated os functions This commit mostly replaces some of the uses of os::args with env::args. 2015-02-16 08:04:02 -06:00			`env::args();`
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			`panic!("please have a nonzero exit status");`
Add tests for issues which can be closed Closes #5275, $4547 2013-07-19 21:01:46 -05:00			`}`