[jira] [Created] (TINKERPOP3-1014) Get rid of Traverser species and TraverserRequirements

["Marko A. Rodriguez (JIRA)" <ji...@apache.org>]

Marko A. Rodriguez created TINKERPOP3-1014:
----------------------------------------------

             Summary: Get rid of Traverser species and TraverserRequirements
                 Key: TINKERPOP3-1014
                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-1014
             Project: TinkerPop 3
          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)