Includes:
6527fb25 Fail parsing checks if var def regexp is bad
0eb6499a Fail parsing checks if the regexp is bad.
ecbc165b Add effcee-fuzz
3842fdc5 Add Bazel build rules.
4bef5dbe Require Python 3
8bf4e0ad Add Clang warning -Wextra-semi

Change-Id: If24758e51cfcc12826dd97550429502441d769e9
Testing: checkbuild.py on Linux

e.g. bad pattern [[FOO:?]]
The question mark is a quantifier that doesn't quantify anything.

BUG=137632977

BUG=129514492

It's only built if you specify a CMake variable pointing
at the FuzzedDataProvider.h source file from LLVM's compiler-rt.

effcee-fuzz runs a simple matcher against standard input.
This can be used to simply and easily reproduce OSS-Fuzz failures.

This adds support for building effcee with Bazel (https://bazel.build).

It automatically pulls the googletest and re2 repositories when building
with Bazel.  I did not add a sha256 attribute to fix the version of the
external repos to get, so by default this tracks top-of-master for those
repos.

It's easy to fix the versions by adding the sha256 attribute that Bazel
suggests when it starts.

Also remove the one extra semicolon it found.

Initial drop of google/effcee from GitHub

Test: checkbuild.py on Linux; unit tests on Windows
Change-Id: Id931fb12867fc221e3f449fc32bec428f54f5c70

For MinGW:
- Don't try to use pthreads
- Statically link the C++ runtime

Use an inlined helper function instead.

Also clang-format affected files.

Fixes #23

- VS2013 doesn't work with Googletest
- Added "What uses Effcee" section
- Update summary status

Python3 requries parentheses around print.

Resolved incorrect unresolved negative checks.
Fixes #14.
Added tests.

- Update the README
- Disable VS 2013 testing

RE2 dropped support for VS 2013.
See https://github.com/google/re2/commit/97957299d1c9f7617cfe653f344536d733582d9e

The fix must be visible to compilation in the effcee/ tree
as well.

But test a debug build only with VS 2017.

Our tests use ::testing::Combine from googletest.  We only care
to run in the environments where that is available, i.e. all reasonably
new compilers and runtimes.

Work around the accidental disabling of ::testing::Combine in VS 2017.
See https://github.com/google/googletest/issues/1352

Error messages are generated by other means, so Check::Description
no longer serves a purpose.

For Visual Studio builds, need to take build configuration
into account.

This will give users more flexibility on what they want to build.

It builds on OSX and Linux:
- OSX: Uses Clang
- Linux: Ubuntu Trusty, Clang 3.6, and GCC

A larger project can add RE2 and googletest before Effcee.
Then Effcee will just reuse those targets.