anchor.diff:  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()`.
  +Match is typically used in conjunction with both `select()` (demonstrated previously) and `where()` (presented here). A `where()`-step allows the user to further constrain the result set provided by `match()`.
   
   [gremlin-groovy,modern]
   ----
  
positive.code:             select('z').values('name')
  ----
  
  IMPORTANT: The `match()`-step is stateless where the variable bindings of the traversal patterns are stored in the path history of the traverser. As such, the variables used over all `match()`-steps within a traversal are globally unique. A benefit of this is that subsequent `where()`, `select()`, `match()`, etc. steps can leverage the same variables in their analysis.
  
  Like all other steps in Gremlin, `match()` is a function and thus, `match()` within `match()` is a natural consequence of Gremlin's functional foundation (i.e. recursive matching).
  
  
negative.code: 
  <1> *Patterns of arbitrary complexity*: `match()` is not restricted to triple patterns or property paths.
  <2> *Recursion support*: `match()` supports the branch-based steps within a pattern, including `repeat()`.
  <3> *Imperative/declarative hybrid*: Before and after a `match()`, it is possible to leverage classic Gremlin traversals.
  
  To extend point #3, it is possible to support going from imperative, to declarative, to imperative, ad infinitum.
  
  