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.

Sign up for GitHub

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

Jump to bottom

Lookup for MappableFlatSet and MappableFlatMultiSet could be further optimised #2

Open
dancooke opened this issue Oct 29, 2017 · 0 comments
Open

Lookup for MappableFlatSet and MappableFlatMultiSet could be further optimised #2

dancooke opened this issue Oct 29, 2017 · 0 comments
Assignees
@dancooke
Labels
enhancement good first issue help wanted

Comments

@dancooke
Copy link
Owner

dancooke commented Oct 29, 2017 •
edited

The performance of MappableFlatSet::overlap_range and MappableFlatMultiSet::overlap_range could potentially be improved by storing bidirectionally sorted and mutually exclusive sub-ranges. This would come at the cost of additional memory usage, so behaviour could potentially be customised at compile time.
@dancooke dancooke self-assigned this Oct 29, 2017
@dancooke dancooke changed the title Lookup is worst case linear for some data sets Lookup is worst case linear Oct 29, 2017
@dancooke dancooke changed the title Lookup is worst case linear Lookup for MappableFlatSet and MappableFlatMultiSet is worst case linear Oct 29, 2017
@dancooke dancooke changed the title Lookup for MappableFlatSet and MappableFlatMultiSet is worst case linear Lookup for MappableFlatSet and MappableFlatMultiSet could be further optimised Oct 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dancooke dancooke

Labels
enhancement good first issue help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dancooke