The CRE2 distribution is a C language wrapper for the RE2 library,
which is implemented in C++. RE2 is a fast, safe, thread-friendly
alternative to backtracking regular expression engines like those used
in PCRE, Perl, and Python.
RE2 is a fast, safe, thread-friendly alternative to backtracking
regular expression engines like those used in PCRE, Perl, and Python.
It is a C++ library.
The check package builds on the standard testing library from Go to offer
a richer testing framework for libraries and applications to use.
gocheck includes features such as:
* Helpful error reporting to aid on figuring problems out (see below)
* Richer test helpers: assertions which interrupt the test immediately,
deep multi-type comparisons, string matching, etc
* Suite-based grouping of tests
* Fixtures: per suite and/or per test set up and tear down
* Benchmarks integrated in the suite logic (with fixtures, etc)
* Management of temporary directories
* Panic-catching logic, with proper error reporting
* Proper counting of successes, failures, panics, missed tests, skips, etc
* Explicit test skipping
* Support for expected failures
* Verbosity flag which disables output caching (helpful to debug hanging
tests, for instance)
* Multi-line string reporting for more comprehensible failures
* Inclusion of comments surrounding checks on failure reports
* Fully tested (it manages to test itself reliably)
Data::Random is a Perl module for generating random data. You might
find it helpful mostly in test programs to easily generate
pseudo-realistic distributions of data.
* not well-maintained in upstream
* active alternative "memoist" gem is available and committed
* the only user mikutter is updated to use the memoist gem
"Include what you use" means this: for every symbol (type, function
variable, or macro) that you use in foo.cc, either foo.cc or foo.h
should #include a .h file that exports the declaration of that symbol.
The include-what-you-use tool is a program that can be built with the
clang libraries in order to analyze #includes of source files to find
include-what-you-use violations, and suggest fixes for them.
The main goal of include-what-you-use is to remove superfluous #includes.
It does this both by figuring out what #includes are not actually needed for
this file (for both .cc and .h files), and replacing #includes with
forward-declares when possible.