Skip to content

No Eq #244

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

Closed
BebeSparkelSparkel opened this issue Dec 23, 2019 · 4 comments
Closed

No Eq #244

BebeSparkelSparkel opened this issue Dec 23, 2019 · 4 comments

Comments

@BebeSparkelSparkel
Copy link

Any thoughts on not depending on the Eq for a faster lookup and smaller footprint when collisions are not a major issue?

@treeowl
Copy link
Collaborator

treeowl commented Dec 23, 2019

Do you have a realistic application where this behavior would actually be acceptable?

@BebeSparkelSparkel
Copy link
Author

I have a tokenized search that has the suggestions paired with a hashable token (some subset of the suggestion's text). In the search if a clash occurs the user will not choose the incorrect suggestions.
If the tokens could be garbage collected and just the hashes remained there would be considerable savings with the amount of memory used.

@treeowl
Copy link
Collaborator

treeowl commented Dec 24, 2019

So what you're really looking for is an IntMap or WordMap implemented as an array-mapped trie?

@BebeSparkelSparkel
Copy link
Author

A very intriguing suggestion. I'll look into array-mapped tries.
Thank you

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

2 participants