7828c3dd28
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]
50 lines
1.7 KiB
Rust
50 lines
1.7 KiB
Rust
// Copyright 2014 The Rust Project Developers. See the COPYRIGHT
|
|
// file at the top-level directory of this distribution and at
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
// option. This file may not be copied, modified, or distributed
|
|
// except according to those terms.
|
|
|
|
// ignore-test
|
|
|
|
// FIXME: this test is being ignored until signals are implemented
|
|
|
|
// This test ensures that the 'detach' field on processes does the right thing.
|
|
// By detaching the child process, they should be put into a separate process
|
|
// group. We test this by spawning a detached process, then killing our own
|
|
// group with a signal.
|
|
//
|
|
// Note that the first thing we do is put ourselves in our own process group so
|
|
// we don't interfere with other running tests.
|
|
|
|
extern crate libc;
|
|
|
|
use std::io::process;
|
|
use std::io::process::Command;
|
|
use std::io::signal::{Listener, Interrupt};
|
|
|
|
fn main() {
|
|
unsafe { libc::setsid(); }
|
|
|
|
// we shouldn't die because of an interrupt
|
|
let mut l = Listener::new();
|
|
l.register(Interrupt).unwrap();
|
|
|
|
// spawn the child
|
|
let mut p = Command::new("/bin/sh").arg("-c").arg("read a").detached().spawn().unwrap();
|
|
|
|
// send an interrupt to everyone in our process group
|
|
unsafe { libc::funcs::posix88::signal::kill(0, libc::SIGINT); }
|
|
|
|
// Wait for the child process to die (terminate it's stdin and the read
|
|
// should fail).
|
|
drop(p.stdin.take());
|
|
match p.wait().unwrap() {
|
|
process::ExitStatus(..) => {}
|
|
process::ExitSignal(..) => panic!()
|
|
}
|
|
}
|