You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Ted Wilmes (JIRA)" <ji...@apache.org> on 2015/12/03 01:08:11 UTC
[jira] [Commented] (TINKERPOP-1014) Get rid of Traverser species
and TraverserRequirements
[ https://issues.apache.org/jira/browse/TINKERPOP-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036917#comment-15036917 ]
Ted Wilmes commented on TINKERPOP-1014:
---------------------------------------
The after was with your latest commit to the TINKERPOP3-1014 branch. I'll hold off on further tests until the requirement aggregation has been removed.
> Get rid of Traverser species and TraverserRequirements
> ------------------------------------------------------
>
> Key: TINKERPOP-1014
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1014
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.1.0-incubating
> Reporter: Marko A. Rodriguez
>
> I think I fell victim to premature optimization. We should not have this hierarchy of {{Traverser}} species. The problem -- its not a hierarchy, its hard to maintain, and the optimization gained is trivial -- at best 3 64-bit references.
> Moreover, we can then get rid of the notion of {{TraverserRequirement}} and thus, speed up the {{Traversal}} compilation. [~twilmes] You noted that gathering {{TraverserRequirements}} was a good chunk of compilation time, right?
> As such, we should just have {{DefaultTraverser}} and it has everything we need where if paths are not used then {{this.path = null}}. Thus, you only suffer the 64-bit reference.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)