tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marko A. Rodriguez (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (TINKERPOP3-760) Make loop counter accessible within repeat()
Date Mon, 03 Aug 2015 15:40:04 GMT

     [ https://issues.apache.org/jira/browse/TINKERPOP3-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marko A. Rodriguez reopened TINKERPOP3-760:
-------------------------------------------

Reopened as this is now in a feature branch.

If we are happy with:

{code}
repeat('i',....repeat('j', .....loops('i'))
{code}

Then I think [~dkuppitz] can merge in the LoopsStep, where {{loops()}} is assumed to be the
"top of the stack." Probably the 99% behavior. When we support {{TraverserRequirement.NESTED_LOOPS}},
we then extend the API (and {{LoopsStep}}) to support {{loops(string)}} (e.g. {{loops('i')}}).

> Make loop counter accessible within repeat()
> --------------------------------------------
>
>                 Key: TINKERPOP3-760
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-760
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.0-incubating
>            Reporter: Daniel Kuppitz
>            Assignee: Daniel Kuppitz
>             Fix For: 3.1.0-incubating
>
>
> Currently we can access the loop counter in a lambda:
> {code}
> .filter {it.loops() < 3}
> {code}
> Would be nice to have a step to access the counter:
> {code}
> .where(loops().is(lt(3)))
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message