Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why not visit items "in-order"? #27

Open
eroller opened this issue Jun 14, 2019 · 0 comments
Open

why not visit items "in-order"? #27

eroller opened this issue Jun 14, 2019 · 0 comments

Comments

@eroller
Copy link

eroller commented Jun 14, 2019

the find* and visit* methods should return intervals "in-order" (i.e. left tree Intervals -> current vector Intervals -> right tree Intervals). This would guarantee the returned Intervals are sorted by start position when the stored Intervals are non-overlapping. Also, it would be nice to have an iterator interface over the tree which would allow users to use some common algorithms more efficiently than having to first create a vector. They could also modify the values stored in the IntervalTree rather than just copying them.

https://github.com/ekg/intervaltree/blob/master/IntervalTree.h#L166-L178

@eroller eroller changed the title why not visit items in order by start position? why not visit items "in-order"? Jun 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant