1
Fork 0

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:
Jacob Pratt 2024-12-17 05:37:30 -05:00 committed by GitHub
commit 1af7df5769
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -613,7 +613,9 @@ impl<'a> ShouldRun<'a> {
self 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 { pub fn path(self, path: &str) -> Self {
self.paths(&[path]) 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` /// 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 /// 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. /// This is analogous to `all_krates`, although `all_krates` is gone now. Prefer [`path`] where possible.
/// ///