[PATCH 11 of 11 sparse] dirstate: integrate sparse matcher with _ignore (API)

[Durham Goode]

On 7/10/17 10:01 AM, Martin von Zweigbergk wrote:
> (For Durham)
>
> On Sat, Jul 8, 2017 at 4:29 PM, Gregory Szorc <gregory.szorc at gmail.com> wrote:
>> # HG changeset patch
>> # User Gregory Szorc <gregory.szorc at gmail.com>
>> # Date 1499555309 25200
>> #      Sat Jul 08 16:08:29 2017 -0700
>> # Node ID 94f98bc84936defadb959e31012555dba170d8cd
>> # Parent  a2867557f9c2314aeea19a946dfb8e167def4fb8
>> dirstate: integrate sparse matcher with _ignore (API)
>
> Why does sparse do it this way instead of intersecting the sparse
> matcher with the user's matcher?

I'm not sure I understand the question.  What is the "user's matcher" 
here? The ignore matcher?

This code produces a matcher that returns true for any file that should 
be ignored.  Since both hgignore files and sparse-ignored files should 
be ignored, I'm not sure how that could be expressed with intersection 
of those two matchers?