book: performance chapter
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 122
- Avg merge
- 10h 37m
- Merged PRs (30d)
- 2
Description
Inspired by this comment and rust-cli/team#29 I've been thinking about adding an in-depth chapter for performance considerations.
The structure would be something like this:
- Common issues and solutions around fast I/O
- how to profile CLI apps (not a full guide but good pointers)
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
Review the book's existing chapter structure and the linked rust-cli/team#29 discussion before defining the chapter's scope. Done means adding an in-depth performance chapter that covers common fast-I/O issues and solutions, plus pointers for profiling CLI applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, documentation, performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100