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 2019/09/23 14:13:00 UTC
[jira] [Closed] (TINKERPOP-1810) Add Lambda.binaryOperator and
Lambda.unaryOperator
[ https://issues.apache.org/jira/browse/TINKERPOP-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP-1810.
---------------------------------------
Fix Version/s: 3.4.4
3.3.9
3.5.0
Resolution: Done
> 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
> Assignee: stephen mallette
> Priority: Major
> Fix For: 3.5.0, 3.3.9, 3.4.4
>
>
> 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
(v8.3.4#803005)