1. About this guide
  2. Getting started
  3. 1. The library team
    1. 1.1. Meetings
    2. 1.2. Membership
    3. 1.3. Reviewing
  5. 2. Building and debugging libraries
  7. 3. The feature lifecycle
    1. 3.1. API Change Proposals
    2. 3.2. Using tracking issues
    3. 3.3. Stabilizing features
    4. 3.4. Deprecating features
  9. 4. Code considerations
    1. 4.1. Design
      1. 4.1.1. Public APIs
      2. 4.1.2. When to add #[must_use]
    3. 4.2. Breaking changes
      1. 4.2.1. Breakage from changing behavior
      2. 4.2.2. Breakage from new trait impls
      3. 4.2.3. #[fundamental] types
      4. 4.2.4. Breakage from changing the prelude
    5. 4.3. Safety and soundness
      1. 4.3.1. Generics and unsafe
      2. 4.3.2. Drop and #[may_dangle]
      3. 4.3.3. std::mem and exclusive references
    7. 4.4. Using unstable language features
      1. 4.4.1. Const generics
      2. 4.4.2. Specialization
    9. 4.5. Performance
      1. 4.5.1. When to #[inline]
  11. 5. Documentation
    1. 5.1. doc alias policy
    2. 5.2. safety comments policy
    3. 5.3. how to write documentation
    4. 5.4. reviewing doc changes
  13. 6. Tools and bots
    1. 6.1. @bors
    2. 6.2. @rust-timer
    3. 6.3. @craterbot

Standard library developers Guide

  • doc alias policy
  • safety comments policy
  • how to write documentation
  • reviewing doc changes