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.
This commit is contained in:
commit
1af7df5769
1 changed files with 4 additions and 2 deletions
|
@ -613,7 +613,9 @@ impl<'a> ShouldRun<'a> {
|
|||
self
|
||||
}
|
||||
|
||||
// single, non-aliased path
|
||||
/// single, non-aliased path
|
||||
///
|
||||
/// Must be an on-disk path; use `alias` for names that do not correspond to on-disk paths.
|
||||
pub fn path(self, path: &str) -> Self {
|
||||
self.paths(&[path])
|
||||
}
|
||||
|
@ -622,7 +624,7 @@ impl<'a> ShouldRun<'a> {
|
|||
///
|
||||
/// This differs from [`path`] in that multiple calls to path will end up calling `make_run`
|
||||
/// multiple times, whereas a single call to `paths` will only ever generate a single call to
|
||||
/// `paths`.
|
||||
/// `make_run`.
|
||||
///
|
||||
/// This is analogous to `all_krates`, although `all_krates` is gone now. Prefer [`path`] where possible.
|
||||
///
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue