Tracking Issue for io_error_input_output_error

[valentynkit]

Feature gate: #![feature(io_error_input_output_error)]

This is a tracking issue for the InputOutputError variant of std::io::ErrorKind, returned for a low-level I/O error. It maps to EIO on Unix and to ERROR_IO_DEVICE on Windows.

Motivation and prior art (PTY EOF handling, storage/VM backends, buck2's own tag for this errno) are in the ACP, linked below.

Public API

// std::io

pub enum ErrorKind {
    // ...
    InputOutputError,
}

Steps / History

• ACP: ACP: Add an io::ErrorKind for low-level I/O errors (EIO) libs-team#824
• Implementation Add io::ErrorKind::InputOutputError #159070
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• The variant name. InputOutputError is what's implemented for now, following the ACP. It isn't settled: DeviceError was proposed, but EIO isn't limited to devices (cuviper). Naming only blocks stabilization, not this issue, so further suggestions are welcome here.

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩