bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

stdio: Document no support for writing to non-blocking stdio/stderr

Browse source 
Printing to stdio/stderr that have been opened with non-blocking
(O_NONBLOCK in linux) can result in an error, which is not handled
by std::io module causing a panic.

Signed-off-by: Usama Arif <usama.arif@bytedance.com>
This commit is contained in:
Usama Arif 2022-09-04 18:43:18 +01:00
parent e7c7aa7288
commit dfbc1f712d
2 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
library/std/src/macros.rs
View file

@ -49,6 +49,9 @@ macro_rules! panic {
///
/// Panics if writing to `io::stdout()` fails.
///
/// Writing to non-blocking stdout can cause an error, which will lead
/// this macro to panic.
///
/// # Examples
///
/// ```
@ -107,6 +110,9 @@ macro_rules! print {
///
/// Panics if writing to [`io::stdout`] fails.
///
/// Writing to non-blocking stdout can cause an error, which will lead
/// this macro to panic.
///
/// [`io::stdout`]: crate::io::stdout
///
/// # Examples
@ -147,6 +153,9 @@ macro_rules! println {
///
/// Panics if writing to `io::stderr` fails.
///
/// Writing to non-blocking stdout can cause an error, which will lead
/// this macro to panic.
///
/// # Examples
///
/// ```
@ -179,6 +188,9 @@ macro_rules! eprint {
///
/// Panics if writing to `io::stderr` fails.
///
/// Writing to non-blocking stdout can cause an error, which will lead
/// this macro to panic.
///
/// # Examples
///
/// ```