anchor.diff:  * fixed width data with zero copy support
   * thread-safe operations
   
  -Note: Chronicle Wire supports debug/transparent combinations like self describing data with zero copy support.
  -
  -To support wire format discovery, the first bytes should have the top-bit set.
  +Note: Chronicle Wire supports debug/transparent combinations like self-describing data with zero copy support.
  +
  +To support wire format discovery, the first bytes should have the top bit set.
   
   == Using Wire
   
  
positive.code: 
  === Features
  
  Chronicle Wire supports a separation of describing what data you want to store and retrieve, and how it should be rendered/parsed. 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,
  * fields that the consumer doesn't expect; optionally parsing them, or ignoring them
  * 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.
  
  Chronicle Wire will also be efficient in the case where any, or all, of the following are true:
  
  * fields are in the order expected
  * fields are the type expected
  * fields names/numbers are not used
  * 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.
  
  
negative.code: The text formats include:
  
  * `YAML` - subset of mapping structures included
  * `JSON` - superset to support serialization
  * `CSV` - superset to support serialization
  * `XML` - planned
  * `FIX` - proposed
  
  Options include:
  
  * field names (for example, JSON), or field numbers (for example, FIX)
  * optional fields with default values that can be dropped
  * zero-copy access to fields - planned
  * thread-safe operations in text - planned
  
  To support wire format discovery, the first byte should be in the `ASCII` range; adding an `ASCII` whitespace if needed.
      
  