Mercurial Mercurial > hg / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | raw | zip | gz | bz2 | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
rustfmt: format the codebase with nightly-2024-07-16
authorRaphaël Gomès <rgomes@octobus.net>
Thu, 18 Jul 2024 12:38:26 +0200
changeset 51705 3876d4c6c79e
parent 51704 550994128204
child 51706 541292a02e09
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).
rust/hg-core/src/dirstate_tree/status.rs file | annotate | diff | comparison | revisions
rust/hg-cpython/src/ancestors.rs file | annotate | diff | comparison | revisions 
--- a/rust/hg-core/src/dirstate_tree/status.rs	Thu Jul 18 12:37:13 2024 +0200
+++ b/rust/hg-core/src/dirstate_tree/status.rs	Thu Jul 18 12:38:26 2024 +0200
@@ -677,14 +677,14 @@
                 // The directory was modified too recently,
                 // don’t cache its `read_dir` results.
                 //
-                // 1. A change to this directory (direct child was
-                //    added or removed) cause its mtime to be set
-                //    (possibly truncated) to `directory_mtime`
+                // 1. A change to this directory (direct child was added or
+                //    removed) cause its mtime to be set (possibly truncated)
+                //    to `directory_mtime`
                 // 2. This `status` algorithm calls `read_dir`
-                // 3. An other change is made to the same directory is
-                //    made so that calling `read_dir` agin would give
-                //    different results, but soon enough after 1. that
-                //    the mtime stays the same
+                // 3. An other change is made to the same directory is made so
+                //    that calling `read_dir` agin would give different
+                //    results, but soon enough after 1. that the mtime stays
+                //    the same
                 //
                 // On a system where the time resolution poor, this
                 // scenario is not unlikely if all three steps are caused
--- a/rust/hg-cpython/src/ancestors.rs	Thu Jul 18 12:37:13 2024 +0200
+++ b/rust/hg-cpython/src/ancestors.rs	Thu Jul 18 12:38:26 2024 +0200
@@ -19,8 +19,8 @@
 //!   `mercurial.ancestor.incrementalmissingancestors`.
 //!
 //!   API differences:
-//!    + it is instantiated with a C `parsers.index`
-//!      instance instead of a parents function.
+//!    + it is instantiated with a C `parsers.index` instance instead of a
+//!      parents function.
 //!    + `MissingAncestors.bases` is a method returning a tuple instead of
 //!      a set-valued attribute. We could return a Python set easily if our
 //!      [PySet PR](https://github.com/dgrunwald/rust-cpython/pull/165)
Mercurial