<commit_before>
Style Guide
===========


Class names should normally use the CapWords convention.

Function names should be lowercase with words separated by underscores.

  http://www.stroustrup.com/bs_faq2.html#Hungarian
  http://www.boost.org/development/requirements.html
  http://google-styleguide.googlecode.com/svn/trunk/cppguide.html
  https://www.python.org/dev/peps/pep-0008/
  https://github.com/styleguide/ruby


The auto keyword should be avoided.

  http://en.wikipedia.org/wiki/C%2B%2B11

<commit_msg>- added rules to style guide<commit_after>
Style Guide
===========


Class names should normally use the CapWords convention.

Function names should be lowercase with words separated by underscores.

  http://www.stroustrup.com/bs_faq2.html#Hungarian
  http://www.boost.org/development/requirements.html
  http://google-styleguide.googlecode.com/svn/trunk/cppguide.html
  https://www.python.org/dev/peps/pep-0008/
  https://github.com/styleguide/ruby


The auto keyword should be avoided.

  http://en.wikipedia.org/wiki/C%2B%2B11


C++11, C++14 and C++17 features can be used when the tool-chain for all
supported distributions provide them.


For API functions it must be avoided to modify parameters and use them as
return values since this is not always obvious and difficult to support in
some target languages.


{'fraction_non_alphanumeric': 0.1101123595505618, 'fraction_numerical': 0.017977528089887642, 'mean_word_length': 4.158301158301159, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 6, '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': '2084163', 'n_tokens_mistral': 442, 'n_tokens_neox': 408, 'n_words': 118}