Skip to content

bootstrap: Remove ShouldRun::paths#152196

Open
jyn514 wants to merge 3 commits intorust-lang:mainfrom
jyn514:remove-paths
Open

bootstrap: Remove ShouldRun::paths#152196
jyn514 wants to merge 3 commits intorust-lang:mainfrom
jyn514:remove-paths

Conversation

@jyn514
Copy link
Member

@jyn514 jyn514 commented Feb 6, 2026

Split out from #151930. I've copied my comment in #151930 (comment) into the commit description.

r? @Zalathar cc @Mark-Simulacrum @Kobzol


Some history about paths(). The original intent @Mark-Simulacrum had
when he introduced PathSet, to my knowledge, was that multiple paths
could be aliases for the same step. That's what rustdoc is doing; both
paths for rustdoc run exactly the same Step, regardless of whether one
or both are present.

That never really caught on. To my knowledge, rustdoc is the only usage
of paths() there's ever been.

Later, in 95503, I repurposed PathSet to mean "each crate in this set
should be passed to Step::make_run in RunConfig". That was not the
previous meaning.

Rustdoc never looks at run.paths in make_run, so it's safe to just treat
it as an alias, like elsewhere in bootstrap. Same for all the other tool
steps.

@rustbot rustbot added A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) labels Feb 6, 2026
@rustbot

This comment has been minimized.

Some history about `paths()`. The original intent Mark-Simulacrum had
when he introduced PathSet, to my knowledge, was that multiple paths
could be aliases for the same step. That's what rustdoc is doing; both
paths for rustdoc run exactly the same Step, regardless of whether one
or both are present.

That never really caught on. To my knowledge, rustdoc is the only usage
of paths() there's ever been.

Later, in 95503, I repurposed PathSet to mean "each crate in this set
should be passed to Step::make_run in RunConfig". That was not the
previous meaning.

Rustdoc never looks at run.paths in make_run, so it's safe to just treat
it as an alias, like elsewhere in bootstrap. Same for all the other tool
steps.
@jieyouxu jieyouxu self-assigned this Feb 6, 2026
Copy link
Member

@jieyouxu jieyouxu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Seems good to me, but will wait for another pair of eyes.

View changes since this review

Co-authored-by: Tshepang Mbambo <hopsi@tuta.io>
@Zalathar
Copy link
Member

Zalathar commented Feb 6, 2026

Looks good, r=me after squashing the fixup commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants