anchor.diff:  serialize closures. The inherently intrinsic and arbitrary nature of closures means 
   that they are not supported by most serialization libraries.
   Initially we started using NetDataContractSerializer as our library of choice,
  -but that eventually took its toll on overall framework performance,
  +but that eventually took its toll on overall performance,
   so we decided to build a new library from scratch.
   
   FsPickler was created with two goals in mind: performance and completeness.
  
positive.code: 
  (**
  
  The `Write` and `Read` functions represent serialization and deserialization implementations
  for values of type `'T`. The `WriteState` and `ReadState` objects enclose serialization state,
  such target/source streams and things like object id generators.
  
  *Pickler combinators* are functions that operate on picklers, generating picklers of more complex types.
  For instance, the following could be a pickler combinator for rank-1 arrays:
  
  *)
  
  
negative.code: In that sense, it was designed with a goal to embrace the imperfect world that is
  the .NET framework in its totality, albeit with an eye for correctness.
  
  At this point, we should acknowledge Anton Tayanovskyy and his great little F#
  snippet [Union-Friendly Generic Binary Serializer](http://www.fssnip.net/6u)
  which served as the initial inspiration for this library.
  
  ## Pickler Combinators
  
  FsPickler is founded on the functional programming notion of picklers and pickler combinators. 
  The concept was originally described in Andrew Kennedy's 
  [Pickler Combinators](http://research.microsoft.com/pubs/64036/picklercombinators.pdf).
  A pickler is essentially the type:
  
  *)
  
  