anchor.diff:  }
   ----
   
  -==== Header Guards
  -Header guards follow the same structure as the namespace and class name
  -for the main class in the file. This should also be the file name.
  -The closing of the header guard should also contain a comment describing
  -what has been closed.
  +=== Header Guards
  +
  +Header guards follow the same structure as the namespace and class name for the
  +main class in the file. This should also be the file name. The closing of the
  +header guard should also contain a comment describing what has been closed.
  +
   [source,cpp]
   ----
   #ifdef __WN_CONTAINERS_DEQUE_H__
  
positive.code: #endif  // __WN_CONTAINERS_DEQUE_H__
  ----
  
  ==== Macros
  Macros should be avoided if possible, but sometimes it is required.
  Other than header guards preprocessor directives should be ALL_CAPS
  separated by "_" characters. In conditional preprocessor sections,
  at the end of the directive a comment should be included describing
  the section that was closed.
  [source,cpp]
  ----
  #define MY_FOO
  
negative.code: struct my_bar;
  ----
  
  === Functions and Class Methods
  
  Free functions follow the same naming conventions as classes. Their names should
  be descriptive of the operation they perform, and longer names should be
  preferred over potentially unclear abbreviations.
  
  === Arguments
  
  Function arguments should follow the same rules as functions and methods, but
  must be prefixed with an `_` denoting they are an input/output to/from this
  method.
  
  [source,cpp]
  ----
  int foo(int _bar, int* _baz);
  ----
  
  === Local Variables
  
  Local variables should be the same as arguments but should omit the underscore.
  
  [source,cpp]
  ----
  int foo() {
  