rust-lang / rust-lang/rfcs

Documentation: quick reference

Open
#693 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

T-doc
Dominant language
Markdown
Stars
6.6k
Forks
1.7k
Avg merge
16h 14m
Merged PRs (30d)
1

Description

Issue by schuyler1d
Tuesday Jan 13, 2015 at 22:02 GMT

For earlier discussion, see https://github.com/rust-lang/rust/issues/21112

This issue was labelled with: A-docs in the Rust repository


Something to think about in terms of the developing suite of documentation is a quick-reference. In python, I use this all the time:
http://rgruet.free.fr/PQR27/PQR2.7.html

Maybe this is more 'for those that live in non-IDE editors', but even as a more advanced user of python, I find it's still a very useful doc -- basically a one-pager of built-in types/syntax/structure and important standard libraries (and maybe even beyond since some important ones will be out of the std library).

Specifically, it aims for compactness rather than complete explanations -- think of it as for someone that has read through the doc and is a beginner/mid-level experience programmer, but 'just can't remember what the method on String is, or "what's the exact command line argument?"

Not sure if it's possible to auto-generate this kind of thing -- maybe a 'combine all the docs' without the explanation strings?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the earlier discussion in Rust issue 21112 and reviewing the current documentation suite. Determine the proposed quick-reference scope for Rust syntax, built-in types, standard libraries, and command-line arguments; the issue does not identify files, tests, or a concrete completion criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.