rust-lang / rust-lang/rustc-dev-guide
Date Reference Triage for 2026-09
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 613
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 39
Description
Procedure
Each of these dates should be checked to see if the docs they annotate are up-to-date. Each date should be updated (in the Markdown file where it appears) to use the current month (September 2026), or removed if the docs it annotates are not expected to fall out of date quickly.
Please check off each date once a PR to update it (and, if applicable, its surrounding docs) has been merged. Please also mention that you are working on a particular set of dates so duplicate work is avoided.
Finally, once all the dates have been updated, please close this issue.
Dates
- src/backend/updating-llvm.md
- 2026-03 line 173
- src/borrow-check/region-inference/member-constraints.md
- 2026-03 line 98
- src/debuginfo/lldb-visualizers.md
- src/diagnostics/error-codes.md
- 2026-03 line 13
- src/diagnostics/translation.md
- src/feature-gate-check.md
- 2026-02 line 11
- src/fuzzing.md
- 2023-03 line 3
- src/hir-typeck/coercions.md
- 2025-12 line 2
- src/opaque-types-type-alias-impl-trait.md
- 2025-05 line 18
- src/overview.md
- 2022-11 line 316
- src/parallel-rustc.md
- src/profiling.md
- 2022-07 line 112
- src/queries/query-evaluation-model-in-detail.md
- 2021-01 line 77
- src/queries/salsa.md
- 2022-11 line 10
- src/query.md
- 2021-07 line 4
- src/rustdoc-internals.md
- src/solve/candidate-preference.md
- 2026-03 line 479
- src/stability.md
- 2024-09 line 40
- src/tests/ci.md
- 2024-10 line 24
- src/tests/directives.md
- src/thir.md
- 2024-01 line 5
- src/traits/chalk.md
- 2022-05 line 4
- src/traits/resolution.md
- 2022-10 line 123
- src/ty-fold.md
- 2024-05 line 1
- src/type-inference.md
- 2023-03 line 69
@rustbot label +C-date-reference-triage +E-easy +E-help-wanted
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the listed line references in the Markdown files under src/ and the surrounding documentation they annotate. For each date, determine whether the content needs a September 2026 update or can have the date removed, then update the relevant files; the work is done when every listed date has a merged PR and the issue checkboxes are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100