You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Daniel Kuppitz (JIRA)" <ji...@apache.org> on 2016/07/13 18:06:20 UTC

[jira] [Commented] (TINKERPOP-1374) Consider making Tree an interface

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

Daniel Kuppitz commented on TINKERPOP-1374:
-------------------------------------------

Why should we have multiple implementations in TinkerPop? In my opinion it would be sufficient to have an order preserving Tree implementation.
A simpler implementation could help to improve performance and memory usage, but what's the thought behind it? Should we have a strategy that makes a decision on which Tree implementation should be used?

> Consider making Tree an interface
> ---------------------------------
>
>                 Key: TINKERPOP-1374
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1374
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: structure
>    Affects Versions: 3.2.0-incubating
>            Reporter: stephen mallette
>            Priority: Minor
>
> Tree should be an interface and we should have:
> * OrderedTree
> * SimpleTree
> * BlahTree



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)