# HG changeset patch
# User Raphaël Gomès <rgomes@octobus.net>
# Date 2019-10-17 12:20:11
# Node ID 6230c70a1863de3c20291a5196f011e6a8465740
# Parent  5d4046594d6fb6f4056d63a4144a32e5bd4ff0c4

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

diff --git a/mercurial/dirstate.py b/mercurial/dirstate.py
--- a/mercurial/dirstate.py
+++ b/mercurial/dirstate.py
@@ -27,7 +27,6 @@ from . import (
     policy,
     pycompat,
     scmutil,
-    sparse,
     txnutil,
     util,
 )
@@ -1115,11 +1114,6 @@ class dirstate(object):
         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:
             (