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