rust/tests/ui/runtime/on-broken-pipe/error.rs

//@ run-pass
//@ aux-build:sigpipe-utils.rs
//@ compile-flags: -Zon-broken-pipe=error
//@ only-unix because SIGPIPE is a unix thing

fn main() {
    extern crate sigpipe_utils;

    // `-Zon-broken-pipe=error` is active, so we expect SIGPIPE to be ignored.
    sigpipe_utils::assert_sigpipe_handler(sigpipe_utils::SignalHandler::Ignore);
}
Support `#[unix_sigpipe = "inherit\|sig_dfl\|sig_ign"]` on `fn main()` This makes it possible to instruct libstd to never touch the signal handler for `SIGPIPE`, which makes programs pipeable by default (e.g. with `./your-program \| head -n 1`) without `ErrorKind::BrokenPipe` errors. 2022-07-05 19:56:22 +02:00			`//@ run-pass`
			`//@ aux-build:sigpipe-utils.rs`
Change `SIGPIPE` ui from `#[unix_sigpipe = "..."]` to `-Zon-broken-pipe=...` In the stabilization attempt of `#[unix_sigpipe = "sig_dfl"]`, a concern was raised related to using a language attribute for the feature: Long term, we want `fn lang_start()` to be definable by any crate, not just libstd. Having a special language attribute in that case becomes awkward. So as a first step towards towards the next stabilization attempt, this PR changes the `#[unix_sigpipe = "..."]` attribute to a compiler flag `-Zon-broken-pipe=...` to remove that concern, since now the language is not "contaminated" by this feature. Another point was also raised, namely that the ui should not leak how it does things, but rather what the end effect is. The new flag uses the proposed naming. This is of course something that can be iterated on further before stabilization. 2024-04-28 18:02:21 +02:00			`//@ compile-flags: -Zon-broken-pipe=error`
Add only-unix to sigpipe tests 2024-04-18 16:50:06 -04:00			`//@ only-unix because SIGPIPE is a unix thing`
tests: Combine unix_sigpipe-not-used.rs and unix_sigpipe-only-feature.rs The only difference between the files is the presence/absence of #![feature(unix_sigpipe)] attribute. Avoid duplication by using revisions instead. 2024-02-09 08:47:47 +01:00
Support `#[unix_sigpipe = "inherit\|sig_dfl\|sig_ign"]` on `fn main()` This makes it possible to instruct libstd to never touch the signal handler for `SIGPIPE`, which makes programs pipeable by default (e.g. with `./your-program \| head -n 1`) without `ErrorKind::BrokenPipe` errors. 2022-07-05 19:56:22 +02:00			`fn main() {`
			`extern crate sigpipe_utils;`

Change `SIGPIPE` ui from `#[unix_sigpipe = "..."]` to `-Zon-broken-pipe=...` In the stabilization attempt of `#[unix_sigpipe = "sig_dfl"]`, a concern was raised related to using a language attribute for the feature: Long term, we want `fn lang_start()` to be definable by any crate, not just libstd. Having a special language attribute in that case becomes awkward. So as a first step towards towards the next stabilization attempt, this PR changes the `#[unix_sigpipe = "..."]` attribute to a compiler flag `-Zon-broken-pipe=...` to remove that concern, since now the language is not "contaminated" by this feature. Another point was also raised, namely that the ui should not leak how it does things, but rather what the end effect is. The new flag uses the proposed naming. This is of course something that can be iterated on further before stabilization. 2024-04-28 18:02:21 +02:00			// `-Zon-broken-pipe=error` is active, so we expect SIGPIPE to be ignored.
Support `#[unix_sigpipe = "inherit\|sig_dfl\|sig_ign"]` on `fn main()` This makes it possible to instruct libstd to never touch the signal handler for `SIGPIPE`, which makes programs pipeable by default (e.g. with `./your-program \| head -n 1`) without `ErrorKind::BrokenPipe` errors. 2022-07-05 19:56:22 +02:00			`sigpipe_utils::assert_sigpipe_handler(sigpipe_utils::SignalHandler::Ignore);`
			`}`