Tracking Issue for io_error_input_output_error
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
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: rust-lang/libs-team#824
- Implementation #159070
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- The variant name.
InputOutputErroris what's implemented for now, following the ACP. It isn't settled:DeviceErrorwas proposed, butEIOisn't limited to devices (cuviper). Naming only blocks stabilization, not this issue, so further suggestions are welcome here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the std::io::ErrorKind public API and read the linked ACP, rust-lang/libs-team#824, plus the feature-lifecycle stabilization guidance. The implementation is identified as #159070; done requires resolving the variant name, completing the final comment period, and preparing a stabilization PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100