microsoft / microsoft/rust-for-dotnet-devs
Consider adding “What should I read next?” section
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 405
- Forks
- 61
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
Consider adding a “What should I read next?” section. While “The Rust Programming Language” is linked throughout, it might be good to call it out again (along with possibly other recommended reading) in case the reader ends up jumping to the end at some point.
/cc @wesleywiser
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 existing references to The Rust Programming Language and the surrounding documentation structure. Add a clearly placed “What should I read next?” section with the relevant recommended reading, then verify that the links and wording fit the book’s navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100