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. The feature lifecycle
    1. 2.1. Landing new features
    2. 2.2. Using tracking issues
    3. 2.3. Stabilizing features
    4. 2.4. Deprecating features
  7. 3. Code considerations
    1. 3.1. Design
      1. 3.1.1. Public APIs
      2. 3.1.2. When to add #[must_use]
    3. 3.2. Breaking changes
      1. 3.2.1. Breakage from changing behavior
      2. 3.2.2. Breakage from new trait impls
      3. 3.2.3. #[fundamental] types
      4. 3.2.4. Breakage from changing the prelude
    5. 3.3. Safety and soundness
      1. 3.3.1. Generics and unsafe
      2. 3.3.2. Drop and #[may_dangle]
      3. 3.3.3. std::mem and exclusive references
    7. 3.4. Using unstable language features
      1. 3.4.1. Const generics
      2. 3.4.2. Specialization
    9. 3.5. Performance
      1. 3.5.1. When to #[inline]
  9. 4. Documentation
    1. 4.1. doc alias policy
  11. 5. Tools and bots
    1. 5.1. @bors
    2. 5.2. @rust-timer
    3. 5.3. @craterbot

Standard library developers Guide

  • doc alias policy