You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/11/17 00:14:10 UTC
[jira] [Created] (TINKERPOP3-967) Support nested-repeat()
structures.
Marko A. Rodriguez created TINKERPOP3-967:
---------------------------------------------
Summary: Support nested-repeat() structures.
Key: TINKERPOP3-967
URL: https://issues.apache.org/jira/browse/TINKERPOP3-967
Project: TinkerPop 3
Issue Type: Improvement
Components: process
Affects Versions: 3.1.0-incubating
Reporter: Marko A. Rodriguez
Assignee: Marko A. Rodriguez
All the internal plumbing is staged for this to happen, we just haven't gone all the way. In short, a {{NESTED_LOOP}} traverser has an internal {{loopStack}} where {{repeat(repeat())}} will have a {{loopStack}} of two. The {{it.loops()}} checks of the internal repeat will always check the top of the stack and when its done repeating will delete its counter off the top of the stack.
[~dkuppitz]'s work on {{LoopStep}} will be backwards compatible. In {{RepeatStep}} we will support:
{code}
repeat('a',out('knows').repeat('b',out('parent')))
{code}
and thus, things like {{loops('a')}} as well as {{times('a',2)}}. Note that naming the loop stack will be a super rare case as most people will just assume standard nested looping semantics with a push/pop stack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)