[jira] [Commented] (TINKERPOP-1810) Add Lambda.binaryOperator and Lambda.unaryOperator

["stephen mallette (JIRA)" <ji...@apache.org>]

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

stephen mallette commented on TINKERPOP-1810:
---------------------------------------------

The problem here is bigger than it appears. Two things: 

1. {{GroovyTranslator}} doesn't know which overload of {[withSack()}} to call. 
2. Given item 1 above, i'm not sure how to implement this without a breaking change to the serializer versions........maybe less of an issue in graphson than in gryo, but that stinks.

I wonder if it's almost better to modify {{SackStrategy}} to use regular old {{Function}} and {{BiFunction}} to get around the serialization problem but that's a lot of API to touch and is less type safe. 



> Add Lambda.binaryOperator and Lambda.unaryOperator
> --------------------------------------------------
>
>                 Key: TINKERPOP-1810
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1810
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.2.6
>            Reporter: Ted Wilmes
>            Priority: Major
>
> While working with sack and lambdas, I found that I could not specify a split ({{UnaryOperator}}) or merge ({{BinaryOperator}}) operator remotely using the {{Lambda}} class helper methods. The sack supplier worked without issue because we already have {{Lambda.supplier}}. I propose we add {{Lambda.unaryOperator}} and {{Lambda.binaryOperator}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)