comparison rust/hg-core/src/dirstate_tree/status.rs @ 51692:771598067be2

rustfmt: format the codebase with nightly-2024-07-16 The CI has moved to a newer nightly, which slightly changes how it wraps comments (which is the very option we use nightly for).
author Raphaël Gomès <rgomes@octobus.net>
date Thu, 18 Jul 2024 12:38:26 +0200
parents 532e74ad3ff6
children 7f0cb9ee0534
comparison
equal deleted inserted replaced
51691:3cb2b5b6626f 51692:771598067be2
675 Ok(Some(directory_mtime)) => directory_mtime, 675 Ok(Some(directory_mtime)) => directory_mtime,
676 Ok(None) => { 676 Ok(None) => {
677 // The directory was modified too recently, 677 // The directory was modified too recently,
678 // don’t cache its `read_dir` results. 678 // don’t cache its `read_dir` results.
679 // 679 //
680 // 1. A change to this directory (direct child was 680 // 1. A change to this directory (direct child was added or
681 // added or removed) cause its mtime to be set 681 // removed) cause its mtime to be set (possibly truncated)
682 // (possibly truncated) to `directory_mtime` 682 // to `directory_mtime`
683 // 2. This `status` algorithm calls `read_dir` 683 // 2. This `status` algorithm calls `read_dir`
684 // 3. An other change is made to the same directory is 684 // 3. An other change is made to the same directory is made so
685 // made so that calling `read_dir` agin would give 685 // that calling `read_dir` agin would give different
686 // different results, but soon enough after 1. that 686 // results, but soon enough after 1. that the mtime stays
687 // the mtime stays the same 687 // the same
688 // 688 //
689 // On a system where the time resolution poor, this 689 // On a system where the time resolution poor, this
690 // scenario is not unlikely if all three steps are caused 690 // scenario is not unlikely if all three steps are caused
691 // by the same script. 691 // by the same script.
692 return Ok(()); 692 return Ok(());