This is for performance; patternmatcher can't easily interpret its results to
make visitchildrenset be the "optimal" set of paths to inspect, but
includematcher can. Since there aren't any special patterns being used here, I
believe that the two matchers are equivalent.
Details
Details
- Reviewers
martinvonz - Group Reviewers
hg-reviewers - Commits
- rHGcd7059d17cb2: context: use includematcher when checking dir/file conflicts
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Event Timeline
Comment Actions
I suppose includematcher can be optimized that way because it's always recursive? Perhaps it should have been called recursivematcher or something.