changeset 43281:6230c70a1863

rust-dirstate-status: use fast-path even with fsmonitor and sparse extensions When I initially ran the tests on my series, there were test failures related to those extensions. Now that the initial series has landed, I felt like going back to those issues because people with performance issues will often want to use fsmonitor and sparse. Either because of flaky tests or because the series has changed so much, I can't seem to reproduce these issues... let's widen the scope of the fast-path. Differential Revision: https://phab.mercurial-scm.org/D7128
author Raphaël Gomès <rgomes@octobus.net>
date Thu, 17 Oct 2019 14:20:11 +0200
parents 5d4046594d6f
children 47946f08e463
files mercurial/dirstate.py
diffstat 1 files changed, 0 insertions(+), 6 deletions(-) [+]
line wrap: on
line diff
--- a/mercurial/dirstate.py	Wed Oct 16 10:14:26 2019 +0200
+++ b/mercurial/dirstate.py	Thu Oct 17 14:20:11 2019 +0200
@@ -27,7 +27,6 @@
     policy,
     pycompat,
     scmutil,
-    sparse,
     txnutil,
     util,
 )
@@ -1115,11 +1114,6 @@
         elif not match.always():
             # Matchers have yet to be implemented
             use_rust = False
-        # We don't yet have a mechanism for extensions
-        elif sparse.enabled:
-            use_rust = False
-        elif not getattr(self, "_fsmonitordisable", True):
-            use_rust = False
 
         if use_rust:
             (