Migrating Content

[KodrAus]

This is a tracking issue for content we'd like to collect up in the standard library dev guide.

Please feel free to edit this issue or leave a comment with other things!

• Anything from https://github.com/rust-lang/rustc-dev-guide?
• https://forge.rust-lang.org/libs/maintaining-std.html

[jyn514]

• How to build/test/document the standard library (x.py build/test/doc --stage 0 library/std respectively)
• How to stabilize a feature (Document stabilization PRs for the standard library rustc-dev-guide#932)
• Where to get help (T-libs on Zulip)

[KodrAus]

• Experts map
• How to add a new tier 3 platform
• How to deprecate a feature
• Documentation style guide
• Considerations for specific APIs (str, slice, Iterator etc)

[KodrAus]

• Triaging contributions and pre-reviewing to look for changes to stable APIs or functional differences
• Interacting with rfcbot

[camelid]

Isn't rfcbot usage common between working on rustc and working on std though?

[KodrAus]

@camelid it probably is, but is pretty central to a lot of std so it might be worth having a stabilization-focused spin on rfcbot?

[KodrAus]

Some other things that would be worth documenting about the code itself:

• The fact that debug assertions aren’t run in user code.
• Platform maintainers and groups to ping for platform-specific code.
• What target features are available for each platform by default.
• Using SIMD in the standard library itself.
• How to add and update submodules.
• Guidance on #[must_use].