<commit_before><!--
  ** File Name:	README.md
  ** Author:	<NAME>
  ** Date:	12/05/2012
  ** Contact:	_<EMAIL>
-->

# Introduction

This library is a collection of utilties (distinct from the standard `utility`
library) which provides a collection of useful header files that make life
easier. A description of each header file is provieded below.

# `format.hpp`

This very small header (125 line) header implements FastFormat's nifty
formatting syntax, without the monolithic frameworks that come with FastFormat,
and its dependency, STLSoft. The functions in this header accept the format
arguments as variadic templates, and invoke `operator<<(ostream&, ...)` to print
out each argument specified in the format string. This header requires a
C++11-conformant compiler.

# `mpl.hpp`

This header contains some useful, general-purpose metafunctions such as
`xu::switch_<std::size_t, class...>`, which can be used to select one of many
types, based on an index.

# `unit_test.hpp`

This header provides some utilties for very basic unit testing. Tests are
implemented as modules, and a set of related modules is gathered in a suite.
Each suite is tied to a particular file; there can only be one suite per file.
<commit_msg>Updated README.<commit_after><!--
  ** File Name:	README.md
  ** Author:	<NAME>
  ** Date:	12/05/2012
  ** Contact:	_<EMAIL>
-->

# Introduction

This library is a collection of utilties (distinct from the standard `utility`
library) which provides a collection of useful header files that make life
easier. A description of each header file is provieded below.

# `format.hpp`

This very small header (125 line) header implements FastFormat's nifty
formatting syntax, without the monolithic frameworks that come with FastFormat,
and its dependency, STLSoft. The functions in this header accept the format
arguments as variadic templates, and invoke `operator<<(ostream&, ...)` to print
out each argument specified in the format string. This header requires a
C++11-conformant compiler.

# `unit_test.hpp`

This header provides some utilties for very basic unit testing. Tests are
implemented as modules, and a set of related modules is gathered in a suite.
Each suite is tied to a particular file; there can only be one suite per file.

{'fraction_non_alphanumeric': 0.07427055702917772, 'fraction_numerical': 0.011494252873563218, 'mean_word_length': 4.466183574879227, 'pattern_counts': {'":': 0, '<': 14, '<?xml version=': 0, '>': 10, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1287734', 'n_tokens_mistral': 641, 'n_tokens_neox': 613, 'n_words': 315}