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 2015/03/26 23:16:52 UTC
[jira] [Reopened] (TINKERPOP3-540) [proposal] Do not expose
filter{}, map{}, sideEffect{}, ...
[ https://issues.apache.org/jira/browse/TINKERPOP3-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette reopened TINKERPOP3-540:
-----------------------------------------
> [proposal] Do not expose filter{}, map{}, sideEffect{}, ...
> -----------------------------------------------------------
>
> Key: TINKERPOP3-540
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-540
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Reporter: Marko A. Rodriguez
> Assignee: Marko A. Rodriguez
> Fix For: 3.0.0.GA
>
>
> The other day, [~mbroecheler] said to me: "Why don't you just get rid of allowing lambdas at all in TP3?"
> Now that all computation is in terms of {{Traversal}}, this would simply entail the following things:
> . No more {{filter{}}}, {{map{}}}, {{flatMap{}}}, {{sideEffect{}}}... the steps would still exist (for extension), but not exposed steps at {{GraphTraversal}}.
> . No more {{by{}}} both function and order.
> Thats it.... at that point, there would be no lambdas in TinkerPop3.
> While this is a 1 hour coding exercise, the ramifications are pretty intense. Please express your thoughts one way or the other.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)