[
https://issues.apache.org/jira/browse/TINKERPOP-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette updated TINKERPOP-2654:
----------------------------------------
Description:
To this point, the {{GroovyTranslator}} has been largely in line with
{{gremlin-language}} in terms of the Gremlin it generates, but maybe it is
worth breaking from that position. To have a succinct {{gremlin-language}} we
might end up situations where we can't easily express what we want in Groovy
without contorting Groovy severely with metaprogramming - we already do this to
some degree with strategies. Perhaps it is best to let them each evolve
separately by having a {{GremlinLangTranslator}}.
This change would open up the idea of having {{Traversal.toString()}} or the
like to have a Gremlin translation rather than the blocky bytecode or step
{{toString()}} which is harder to read.
was:To this point, the {{GroovyTranslator}} has been largely in line with
{{gremlin-language}} in terms of the Gremlin it generates, but maybe it is
worth breaking from that position. To have a succinct {{gremlin-language}} we
might end up situations where we can't easily express what we want in Groovy
without contorting Groovy severely with metaprogramming - we already do this to
some degree with strategies. Perhaps it is best to let them each evolve
separately by having a {{GremlinLangTranslator}}.
> Add a GremlinLangTranslator
> ---------------------------
>
> Key: TINKERPOP-2654
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2654
> Project: TinkerPop
> Issue Type: Improvement
> Components: translator
> Affects Versions: 3.5.1
> Reporter: Stephen Mallette
> Priority: Major
>
> To this point, the {{GroovyTranslator}} has been largely in line with
> {{gremlin-language}} in terms of the Gremlin it generates, but maybe it is
> worth breaking from that position. To have a succinct {{gremlin-language}} we
> might end up situations where we can't easily express what we want in Groovy
> without contorting Groovy severely with metaprogramming - we already do this
> to some degree with strategies. Perhaps it is best to let them each evolve
> separately by having a {{GremlinLangTranslator}}.
> This change would open up the idea of having {{Traversal.toString()}} or the
> like to have a Gremlin translation rather than the blocky bytecode or step
> {{toString()}} which is harder to read.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
