anchor.diff:  Select Step
   ~~~~~~~~~~~
   
  -There are two use cases for `select`-step (*map*).
  +There are two use cases for `select()`-step (*map*).
   
   . Select named steps within a path (as defined by `as()` in a traversal).
   . Select objects out of a `Map<String,Object>` flow (i.e. a sub-map).
  
positive.code: <2> Select will grab both as-named steps and `Map<String,Object>` entries.
  <3> The same `List<String>` selectivity can be used as demonstrated in the previous example.
  <4> If a single selection is used, then the object is emitted not wrapped in a map. Useful for continuing the traversal process without having to do a map projection.
  
  [[store-step]]
  Store Step
  
negative.code:             select(['a','c']){it.value('name')}
  ==>[a:marko, c:ripple]
  
  WARNING: Currently, `match()` does not operate within a multi-JVM <<graphcomputer,GraphComputer>> OLAP environment. Future work includes a linearization <<traversalstrategy,TraversalStrategy>> for `match()`.
  
  [[using-where-with-match]]
  Using Where with Match
  ^^^^^^^^^^^^^^^^^^^^^^
  
  Match is typically used in conjunction with both `select()` (demonstrated previously) and `where()` (presented here). A `where()` allows the user to further constrain the result set provided by `match()`.
  
  