[
https://issues.apache.org/jira/browse/TINKERPOP-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432392#comment-17432392
]
Stephen Mallette commented on TINKERPOP-1853:
---------------------------------------------
I see what you're saying. The {{Translator}} in C# gets users about 90% of the
way to a working traversal I think. There's a lot of hard-coded odds and ends
to make it even do what it is doing today. I suppose that the question is, do
we sacrifice translation features for better type safety? [~krlawrence] any
thoughts on this one?
> 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.3.4#803005)
