[jira] [Commented] (TINKERPOP3-802) Provide sack(object) so that the sack can be directly set.

["Marko A. Rodriguez (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP3-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715477#comment-14715477 ] 

Marko A. Rodriguez commented on TINKERPOP3-802:
-----------------------------------------------

I have made it so that {{SackElementValueStep}] and {{SackObjectStep}} are now just {{SackValueStep}}. We now support:

{code}
g.V()...sack(mult).by('weight')
{code}

For backwards compatibility, the original model has been deprecated.

{code}
g.V()...sack(mult,'weight')
{code}

What is nice about the new model is that by-modulation can be any arbitrary traversal. Now we just need a {{sack(set).by(constant("x"))}} and this will be done. However, I don't want to create a new operator... :( Will think a bit.

> Provide sack(object) so that the sack can be directly set.
> ----------------------------------------------------------
>
>                 Key: TINKERPOP3-802
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-802
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.0-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>
> Currently, to declare a sack value to be {{X}} you have to do this:
> {code}
> ...sack{a,b -> X}
> {code}
> This is lame. We should have:
> {code}
> sack(X)
> {code}



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