bytecodealliance / bytecodealliance/wstd
Introduce BufReader, BufWriter
Open
feature-request
- Dominant language
- Rust
- Stars
- 133
- Forks
- 19
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 5
Description
Each async "std" (tokio, async-std, smol, presumably there are others) ends up introducing its own BufReader and BufWriter. Post #37, wstd needs one as well.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by inspecting wstd's existing async standard-library APIs and comparing BufReader and BufWriter in tokio, async-std, and smol; done means wstd provides both requested buffering types with agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100