Add an out-of-bounds variant to ErrorKind
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
There isn't a variant of std::io::ErrorKind that maps cleanly to the return value EFBIG of write(2); That is, an error value that indicates that a write is too large for the resource.
I think adding an OutOfBounds variant (or similar) would be better than lumping this kind of error together with others as Other.
Contributor guide
No contributing guide indexed for this repository
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 by reviewing std::io::ErrorKind and the write(2)/EFBIG mapping described in the issue, including how the existing Other variant is used. Define the proposed variant and its intended error semantics, then document the API decision as an RFC; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100