i18n/polib.LICENSE

match: add `filepath:` pattern to match an exact filepath relative to the root

It's useful in certain automated workflows to make sure we recurse in
directories whose name conflicts with files in other revisions.

In addition it makes it possible to avoid building a potentially costly regex,
improving performance when the set of files to match explicitly is large.

The benchmark below are run in the following configuration :
 # data-env-vars.name             = mozilla-central-2018-08-01-zstd-sparse-revlog
 # benchmark.name                 = files
 # benchmark.variants.rev         = tip
 # benchmark.variants.files       = all-list-filepath-sorted
 # bin-env-vars.hg.flavor         = no-rust

It also includes timings using the re2 engine (through the `google-re2` module)
to show how much can be saved by just using a better regexp engine.


Pattern                time (seconds)        time using re2
-----------------------------------------------------------
just "."                0.4                    0.4
list of "filepath:…"    1.3                    1.3
list of "path:…"       25.7                    3.9
list of patterns       29.7                   10.4

As you can see, Without re2, using "filepath:" instead of "path:" is a huge
win. With re2, it is still about three times faster to not have to build the
regex.

copyright (c) 2006-2010 David JEAN LOUIS

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.