Hi guys,
looking at the second example in the following section of the docs I
noticed a semantic overlap between match and where:
http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#using-where-with-match
traversal = g.V().match('a', __.as('a').out('created').as('b'), __.as('b'
).in('created').as('c')). where(__.as('a').out('knows').as('c')). select('a'
,'c').by('name');
The provided where clause could also have been folded into the actual
traversal to yield the same result.
I wonder:
1) Is there a way to avoid this ambiguity?
2) or should we simply not promote it in the docs. As the docs are
currently written I am worried that users might get confused as to how
match steps are supposed to be written.
Thanks,
Matthias
