Skip to content

Commit 1af7df5

Browse files
authored
Rollup merge of #134409 - RalfJung:bootstrap-comment, r=jieyouxu
bootstrap: fix a comment I don't actually know if this is right, though... but "a single call to `paths` will only ever generate a single call to `paths`" just does not make sense.
2 parents 3d0e5e0 + 7dbfe4d commit 1af7df5

File tree

1 file changed

+4
-2
lines changed
  • src/bootstrap/src/core/builder

1 file changed

+4
-2
lines changed

Diff for: src/bootstrap/src/core/builder/mod.rs

+4-2
Original file line numberDiff line numberDiff line change
@@ -613,7 +613,9 @@ impl<'a> ShouldRun<'a> {
613613
self
614614
}
615615

616-
// single, non-aliased path
616+
/// single, non-aliased path
617+
///
618+
/// Must be an on-disk path; use `alias` for names that do not correspond to on-disk paths.
617619
pub fn path(self, path: &str) -> Self {
618620
self.paths(&[path])
619621
}
@@ -622,7 +624,7 @@ impl<'a> ShouldRun<'a> {
622624
///
623625
/// This differs from [`path`] in that multiple calls to path will end up calling `make_run`
624626
/// multiple times, whereas a single call to `paths` will only ever generate a single call to
625-
/// `paths`.
627+
/// `make_run`.
626628
///
627629
/// This is analogous to `all_krates`, although `all_krates` is gone now. Prefer [`path`] where possible.
628630
///

0 commit comments

Comments
 (0)