You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Florian Hockmann (Jira)" <ji...@apache.org> on 2022/09/29 10:22:00 UTC

[jira] [Closed] (TINKERPOP-1853) Use generic version of ITraversal for arguments in Traversal API

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

Florian Hockmann closed TINKERPOP-1853.
---------------------------------------
    Resolution: Won't Do

As noted, we would probably have to break the translation of Gremlin traversals to .NET to make this possible and this feature doesn't seem important enough to do that.

> Use generic version of ITraversal for arguments in Traversal API
> ----------------------------------------------------------------
>
>                 Key: TINKERPOP-1853
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1853
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: dotnet
>    Affects Versions: 3.3.0, 3.2.6
>            Reporter: Florian Hockmann
>            Assignee: Florian Hockmann
>            Priority: Minor
>
> Currently, we use {{ITraversal}} as the type for arguments in the traversal API of Gremlin.Net when a traversal is expected:
> {code}
> public GraphTraversal< S , E2 > Choose<E2> (ITraversal traversalPredicate, ITraversal trueChoice)
> {code}
> The Java equivalent is more useful as it only allows {{Traversal<?, E2>}} for the second argument:
> {code}
> public default <E2> GraphTraversal<S, E2> choose(final Traversal<?, ?> traversalPredicate, final Traversal<?, E2> trueChoice)
> {code}
> We should also use the generic type {{ITraversal<object, E2>}} in Gremlin.Net in those cases. Then it wouldn't be necessary to specify the type for the arguments and the step as it can be interfered from the type of the arguments.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)