Repository navigation
Migrating Content #1
Description
Activity
- How to build/test/document the standard library (
x.py build/test/doc --stage 0 library/stdrespectively) - How to stabilize a feature (Document stabilization PRs for the standard library rustc-dev-guide#932)
- Where to get help (T-libs on Zulip)
- How to build/test/document the standard library (
- Experts map
- How to add a new tier 3 platform
- How to deprecate a feature
- Documentation style guide
- Considerations for specific APIs (
str,slice,Iteratoretc)
- Triaging contributions and pre-reviewing to look for changes to stable APIs or functional differences
- Interacting with rfcbot
Isn't rfcbot usage common between working on rustc and working on std though?
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].
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!