rust-lang / rust-lang/rust-clippy
Lint request: unbuffered I/O usage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
I and several other beginners have run into the surprising issue that Rust's default file reading and writing methods are unbuffered and buffered IO is purely opt-in with this language. It may be useful to add a lint to warn users about this, as it seems to come up from time to time when comparing programs to other languages such as Python.
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 by reviewing existing Clippy lint implementations and the Rust file-reading and writing APIs discussed in the issue. Define which unbuffered I/O usage should trigger a warning, then verify that the lint distinguishes intended usage and has coverage for the reported beginner scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100