You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2016/12/01 17:40:58 UTC
[jira] [Closed] (TINKERPOP-1580) Resolve naming collisions for
static imports in the Gremlin language
[ https://issues.apache.org/jira/browse/TINKERPOP-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP-1580.
---------------------------------------
Resolution: Duplicate
> Resolve naming collisions for static imports in the Gremlin language
> --------------------------------------------------------------------
>
> Key: TINKERPOP-1580
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1580
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.3
> Reporter: stephen mallette
>
> This may not be a breaking change - it can likely be done with deprecation along the 3.2.x line. The problem is that static imports collide in the {{GremlinScriptEngine}} and therefore there are not only situations where certain imports will be "hidden" but it can cause the system behave in non-deterministic fashion depending on the {{ScriptEngine}}. For example, groovy's compiler seems to only be able to detect the difference between {{Column.values}} and {{__.values()}} if wildcards are used. If they are imported directly then one of the other will fail.
> Here's a list of the troublemaker names that collide across different methods/enums: or,and,id,values,key,local,value,sum,min,max.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)