anchor.diff:  * 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.
  -    
  +
   == Binary Formats
   
   The binary formats include:
  
positive.code: 
  Chronicle Wire allows (and encourages) objects to be re-used in order to reduce allocation rates.
  
  When a marshallable object is re-used or initialised by the framework, it is first reset by way of `Wires.reset()`. In the case of most DTOs with simple scalar values, this will not cause any issues. However, more complicated objects with object instance fields may experience undesired behaviour.
  
  In order to `reset` a marshallable object, the process is as follows:
  
     1. create a new instance of the object to be reset
     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 (for example, `int`, `Long`, `String`), a mutable field such as `ByteBuffer` will cause problems. Consider the following case:
  
  [source,java]
  ----
  
negative.code: 
  Chronicle Wire offers the ability to bind a reference to a fixed value of a field, and perform atomic operations on that field; for example, volatile read/write, and compare-and-swap.
  
  [source,Java]
  ----
     // field to cache the location and object used to reference a field.
     private LongValue counter = null;
  