Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
d5061a8
make date-check entries clickable
tshepang Dec 17, 2025
5fbb39c
Fix function formatting in src/overview.md
reddevilmidzy Dec 23, 2025
f61c7f7
Merge pull request #2707 from reddevilmidzy/fix
BoxyUwU Dec 24, 2025
611bece
Update 'Working groups' to 'Working areas' in docs
reddevilmidzy Dec 24, 2025
db48a24
Merge pull request #2708 from reddevilmidzy/wa
tshepang Dec 24, 2025
5a4f1c3
put back line numbers
tshepang Dec 27, 2025
a7bdf0d
Merge pull request #2702 from rust-lang/tshepang/make-date-check-entr…
tshepang Dec 27, 2025
287d4df
make ci step more simple
tshepang Dec 27, 2025
e671d41
Merge pull request #2710 from rust-lang/tshepang/fix-date-check-links
tshepang Dec 27, 2025
61a8b6b
stop checking if PRs are behind
tshepang Dec 28, 2025
cfd4d09
Prepare for merging from rust-lang/rust
invalid-email-address Dec 29, 2025
da9d86c
Merge ref '7fefa09b90ca' from rust-lang/rust
invalid-email-address Dec 29, 2025
dc85816
Add link for perf run Zulip channel
reddevilmidzy Dec 29, 2025
866598d
Add guidance on suppressing warnings in tests
reddevilmidzy Dec 29, 2025
ed66fcb
Merge pull request #2715 from reddevilmidzy/warn
BoxyUwU Dec 29, 2025
5076810
Merge pull request #2713 from rust-lang/rustc-pull
tshepang Dec 29, 2025
90e5a5d
Merge pull request #2714 from reddevilmidzy/perf-run
BoxyUwU Dec 30, 2025
da0ad30
Merge pull request #2712 from rust-lang/tshepang-patch-1
jieyouxu Jan 1, 2026
c27addb
Prepare for merging from rust-lang/rust
invalid-email-address Jan 2, 2026
874cbe6
Merge ref '85c8ff69cb3e' from rust-lang/rust
invalid-email-address Jan 2, 2026
085d6b8
Merge pull request #2717 from rust-lang/rustc-pull
tshepang Jan 2, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions src/doc/rustc-dev-guide/.github/workflows/date-check.yml
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,7 @@ jobs:
rustup update stable

- name: Run `date-check`
working-directory: ci/date-check
run: |
cargo run -- ../../src/ > ../../date-check-output.txt
run: cargo run --manifest-path ci/date-check/Cargo.toml . > date-check-output.txt

- name: Open issue
uses: actions/github-script@v7
Expand Down
8 changes: 6 additions & 2 deletions src/doc/rustc-dev-guide/ci/date-check/src/main.rs
Original file line number Diff line number Diff line change
Expand Up @@ -153,9 +153,13 @@ fn main() {
println!();

for (path, dates) in dates_by_file {
println!("- {}", path.strip_prefix(&root_dir_path).unwrap_or(&path).display(),);
let path = path.strip_prefix(&root_dir_path).unwrap_or(&path).display();
println!("- {path}");
for (line, date) in dates {
println!(" - [ ] line {}: {}", line, date);
let url = format!(
"https://github.com/rust-lang/rustc-dev-guide/blob/main/{path}?plain=1#L{line}"
);
println!(" - [ ] {date} [line {line}]({url})");
}
}
println!();
Expand Down
2 changes: 1 addition & 1 deletion src/doc/rustc-dev-guide/rust-version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
2dc30247c5d8293aaa31e1d7dae2ed2fde908ada
85c8ff69cb3efd950395cc444a54bbbdad668865
4 changes: 2 additions & 2 deletions src/doc/rustc-dev-guide/src/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ The following tasks are doable without much background knowledge but are incredi
to read a part of the code and write doc comments for it.
This will help you to learn some part of the compiler while also producing a useful artifact!
- [Triaging issues][triage]: categorizing, replicating, and minimizing issues is very helpful to the Rust maintainers.
- [Working groups][wg]: there are a bunch of working groups on a wide variety
- [Working areas][wa]: there are a bunch of working areas on a wide variety
of rust-related things.
- Answer questions on [users.rust-lang.org][users], or on [Stack Overflow][so].
- Participate in the [RFC process](https://github.com/rust-lang/rfcs).
Expand All @@ -191,7 +191,7 @@ The following tasks are doable without much background knowledge but are incredi
[so]: http://stackoverflow.com/questions/tagged/rust
[community-library]: https://github.com/rust-lang/rfcs/labels/A-community-library
[wd]: ./contributing.md#writing-documentation
[wg]: https://rust-lang.github.io/compiler-team/working-groups/
[wa]: https://forge.rust-lang.org/compiler/working-areas.html
[triage]: ./contributing.md#issue-triage

## Cloning and Building
Expand Down
4 changes: 2 additions & 2 deletions src/doc/rustc-dev-guide/src/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,10 +50,10 @@ preserves full fidelity information for both IDEs and procedural macros
The *parser* [translates the token stream from the `lexer` into an Abstract Syntax
Tree (AST)][parser]. It uses a recursive descent (top-down) approach to syntax
analysis. The crate entry points for the `parser` are the
[`Parser::parse_crate_mod()`][parse_crate_mod] and [`Parser::parse_mod()`][parse_mod]
[`Parser::parse_crate_mod`][parse_crate_mod] and [`Parser::parse_mod`][parse_mod]
methods found in [`rustc_parse::parser::Parser`]. The external module parsing
entry point is [`rustc_expand::module::parse_external_mod`][parse_external_mod].
And the macro-`parser` entry point is [`Parser::parse_nonterminal()`][parse_nonterminal].
And the macro-`parser` entry point is [`Parser::parse_nonterminal`][parse_nonterminal].

Parsing is performed with a set of [`parser`] utility methods including [`bump`],
[`check`], [`eat`], [`expect`], [`look_ahead`].
Expand Down
1 change: 1 addition & 0 deletions src/doc/rustc-dev-guide/src/tests/best-practices.md
Original file line number Diff line number Diff line change
Expand Up @@ -153,6 +153,7 @@ This may include remarks on:
- Try to make sure the test is as minimal as possible.
- Minimize non-critical code and especially minimize unnecessary syntax and type
errors which can clutter stderr snapshots.
- Use `#![allow(...)]` or `#![expect(...)]` to suppress unrelated warnings.
- Where possible, use semantically meaningful names (e.g. `fn
bare_coverage_attributes() {}`).

Expand Down
4 changes: 3 additions & 1 deletion src/doc/rustc-dev-guide/src/tests/perf.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,9 @@ To evaluate the performance impact of a PR, write this comment on the PR:
> repository](https://github.com/rust-lang/team) with the `perf = true` value in
> the `[permissions]` section (and bors permissions are also required). If you
> are not on one of those teams, feel free to ask for someone to post it for you
> (either on Zulip or ask the assigned reviewer).
> (either on [Zulip][perf run] or ask the assigned reviewer).

[perf run]: https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp/topic/perf.20run

This will first tell bors to do a "try" build which do a full release build for
`x86_64-unknown-linux-gnu`. After the build finishes, it will place it in the
Expand Down
3 changes: 0 additions & 3 deletions src/doc/rustc-dev-guide/triagebot.toml
Original file line number Diff line number Diff line change
Expand Up @@ -58,9 +58,6 @@ allow-unauthenticated = [
# Documentation at: https://forge.rust-lang.org/triagebot/issue-links.html
[issue-links]

[behind-upstream]
days-threshold = 7

# Enable triagebot (PR) assignment.
# Documentation at: https://forge.rust-lang.org/triagebot/pr-assignment.html
[assign]
Expand Down
Loading