anchor.diff:  
   === Features
   
  -Chronicle Wire supports a separation of describing what data you want to store and retrieve, and how it should be rendered/parsed. Chronicle Wire handles a variety of formatting options, for a wide range of formats.
  -
  -A key aim of Chronicle Wire is to support schema changes.  It should make reasonable attempts to handle:
  +Chronicle Wire supports a separation of describing what data you want to store and retrieve, and how it should be rendered/parsed.
  +Chronicle Wire handles a variety of formatting options, for a wide range of formats.
  +
  +A key aim of Chronicle Wire is to support schema changes.
  +It should make reasonable attempts to handle:
   
   * optional fields
   * fields in a different order
  
positive.code: * self-describing types are not needed
  * random access of data values is supported.
  
  Chronicle Wire is designed to make it easy to convert from one wire format to another. For example, you can use fixed-width binary data in memory for performance, and variable-width or text over the network. Different TCP connections could use different formats.
    
  Chronicle Wire also supports hybrid wire formats.  For example, you can have one format embedded in another.
  
  == Support
  
  
negative.code: * more or less data than expected; in field-less formats
  * reading a different type to the one written
  * updating fixed-length fields, automatically where possible using a `bound` data structure.
  * dynamic updates of Enums or objects passed-by-name
  
  Chronicle Wire will also be efficient where any, or all, of the following points are true:
  
  