-
-
Notifications
You must be signed in to change notification settings - Fork 17.3k
[x.py] Option to not rebuild compiler #46180
Copy link
Copy link
Closed
Labels
C-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.
Description
Activity
Metadata
Metadata
Assignees
Labels
C-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.
One of the biggest paper cuts when working on Rust documentation is that x.py is really really eager to rebuild the compiler, even when the only thing that is changing one line in documentation or update a test.
As such, it would be extremely beneficial to those writing docs and tests (including doctests!) if we could have a flag where we as the end user of the flag promise we're not changing actual compiler code, so please use the previous still good compiler to rebuild the docs with our changes. Note that the option doesn't have to actually rebuild the documentation, as ideally we'd just combine it with
x.py docandx.py test src/libstdas needed.cc @rust-lang/infra