# HG changeset patch
# User Pierre-Yves David <pierre-yves.david@octobus.net>
# Date 1676889422 -3600
# Node ID c175b48574986abfe96104588c5126dcc903d66b
# Parent  dae8dda6f5822cdcac61a24e78f7935de7af9618
dirstate: add a comment about the semantic of `dirstate.clear`

This method is weird, lets flag it as such.

diff -r dae8dda6f582 -r c175b4857498 mercurial/dirstate.py
--- a/mercurial/dirstate.py	Mon Feb 20 14:05:19 2023 +0100
+++ b/mercurial/dirstate.py	Mon Feb 20 11:37:02 2023 +0100
@@ -858,6 +858,9 @@
     # XXX since this make the dirstate dirty, we should enforce that it is done
     # withing an appropriate change-context that scope the change and ensure it
     # eventually get written on disk (or rolled back)
+    # XXX this method is barely used, as a result:
+    # - its semantic is unclear
+    # - do we really needs it ?
     def clear(self):
         self._map.clear()
         self._dirty = True