Editions (RFC 2052)

Open
#281 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the issue checklist and the mdbook test question. Determine the intended plan for documenting editions, verify how the examples should become Rust 2018-compatible, and decide how Rust 2015 differences should be presented. Done means the edition behavior, compatible examples, and chosen treatment of Rust 2015 differences are documented.

Written by the indexing model from the issue text.

Description

A-editions RFC Stabilization Docs

Raising this now so that we can decide what the plan is here.

  • Document editions
  • Make sure that all examples are using Rust 2018 compatible code (paths are the main concern).
    • How do editions interact with mdbook test?
  • Documenting Rust 2015 differences (assuming that the reference moves to Rust 2018 by default)
    • Should these be inline, or in an appendix.
Dominant language
Rust
Stars
1.6k
Forks
607
Avg merge
1d 1h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

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.

More from rust-lang/reference

All issues in rust-lang/reference

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.