[ 
https://issues.apache.org/jira/browse/TINKERPOP-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283987#comment-17283987
 ] 

ASF GitHub Bot commented on TINKERPOP-2452:
-------------------------------------------

spmallette commented on pull request #1387:
URL: https://github.com/apache/tinkerpop/pull/1387#issuecomment-778463431


   I think I managed to get everything with this last push. Thanks again for 
the detailed review @FlorianHockmann . I'm so glad this actually worked. I was 
wondering how this functionality was going to even shape up for C# with the 
generics. I'm still wondering what additional problems are lurking in here 
though. After this merges I might add some more translator documentation. We 
might want to point out that C# has some experimental aspects to it as it is 
the one that is most likely to hit conditions we hadn't considered given the 
way C# works. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> DotNetTranslator for Java
> -------------------------
>
>                 Key: TINKERPOP-2452
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2452
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: translator
>    Affects Versions: 3.4.8
>            Reporter: Stephen Mallette
>            Priority: Major
>
> Add a {{DotNetpTranslator}} to Java to translate Gremlin into C#. This one 
> may be tricky given the need to often specify generics in C#. Of course, even 
> if the implementation got someone most of the way to a translation and they 
> had to specify the generics themselves it would be considerably less work 
> than what they are in store for today.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to