anchor.diff:  
   == About
   
  -Chronicle Wire is a a Wire Format abstraction Library, The purpose of Chronicle Wire is to combine a number of concerns in a consistent manner:
  +Chronicle Wire is a a Wire Format abstraction library, The purpose of Chronicle Wire is to address the following concerns in a consistent manner:
   
   - Application configuration. (Using YAML)
   - Data serialization (YAML, binary YAML, JSON, Raw binary data, CSV)
   - Accessing off-heap memory in a thread-safe manner. (Bind to shared off-heap memory)
  -- High performance data exchange via binary formats. Only include as much meta data as you need.
  +- High performance data exchange using binary formats. Only include as much meta data as you need.
   
   == Design
   
  
positive.code:    2. copy all fields from the new instance to the existing instance
     3. the existing instance is now considered 'reset' back to default values
  
  The object created in step `1` is cached for performance reasons, meaning that both the new and existing
  instance of the marshallable object could have a reference to the same object.
  
  While this will not be a problem for primitive or immutable values (e.g. `int`, `Long`, `String`), a mutable
  field such as `ByteBuffer` will cause problems. Consider the following case:
  
  [source,java]
  ----
  
negative.code: 
  Often you want to use these interchangeably.
  
  - Configuration includes aliased type information.  This supports easy extension by adding new classes/versions, and cross-platform using type aliasing.
  - By supporting types, a configuration file can bootstrap itself. You control how the configuration file is decoded. See https://github.com/OpenHFT/Chronicle-Engine/blob/master/demo/src/main/resources/engine.yaml[`engine.yaml`].
  - To send the configuration of a server to a client, or from a client to a server.
  - To store the configuration of a data store in its header.
  