Tracking Issue for io_error_too_many_open_files
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-unimplemented
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(io_error_too_many_open_files)]
This is a tracking issue for the TooManyOpenFiles variant of std::io::ErrorKind,
returned when the process or the whole system has reached its limit on open files or
sockets. It maps to EMFILE (per-process) and ENFILE (system-wide) on Unix, and to
ERROR_TOO_MANY_OPEN_FILES and WSAEMFILE on Windows.
Public API
// std::io
pub enum ErrorKind {
// ...
TooManyOpenFiles,
}
Steps / History
- ACP: rust-lang/libs-team#818
- Implementation: https://github.com/rust-lang/rust/pull/158326
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
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
Review the std::io::ErrorKind API, the completed implementation PR, and the stabilization process linked in the issue. Check the final comment period requirements and prepare the remaining stabilization work; done means the feature gate can be stabilized with no unresolved questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100