std::fs::File error msg
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
I recently had a bug with File::open() vs File::create(). I had called File::open() and then tried to call write_all() to that file. I received the error message "Bad File Descriptor". Then, at some point, I realized that I have to call File::create(), even if the file exists already. I am wondering if it would be possible to display a better error message that would suggest that I had opened a file in read-only mode, and not write mode.
I would be happy to help with a patch for this. Thanks!
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 tracing the File::open(), File::create(), and write_all() entry points to see how a read-only write failure becomes "Bad File Descriptor." Determine whether the error can identify read-only mode across supported platforms; done means presenting a more helpful message for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100