[
https://issues.apache.org/jira/browse/TINKERPOP3-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP3-788.
-----------------------------------------
Resolution: Won't Fix
This is going against what we are planning for Gremlin DSL. In short, there
will be a limited set of steps that Gremlin supports and these are called the
"instruction set" of the Gremlin virtual machine. These steps (and their
parameters) can be specified via a text representation. This means that other
languages will be able to send traversals and get results back. We need to
avoid {{Person.class}} as that is too JVM specific.
In short, there will be NO domain objects in TinkerPop3. {{curry()}} step goes
against this.
> Curry step
> ----------
>
> Key: TINKERPOP3-788
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-788
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.0-incubating
> Reporter: Matt Frantz
> Assignee: Marko A. Rodriguez
>
> The {{curry}} step would be a way to introduce user-defined types without
> lambdas.
> {noformat}
> <E2> GraphTraversal<S, E2> curry(Class<? extends E2> c);
> {noformat}
> It would be the equivalent of a {{map}} step that instantiates the class with
> a single constructor argument provided by the traverser.
> {noformat}
> g.V().curry(MyType.class)
> g.V().<MyType>map{it -> new MyType(it.get())}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
