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

v2 LookupSet #586

Closed
austinabell opened this issue Sep 23, 2021 · 0 comments · Fixed by #654
Closed

v2 LookupSet #586

austinabell opened this issue Sep 23, 2021 · 0 comments · Fixed by #654
Assignees

Comments

@austinabell
Copy link
Contributor

Unlike current LookupSet, API should match HashSet as much as possible (although most functionality won't be possible until UnorderedSet is implemented because keys won't be tracked).

Similar to #487 except instead of writing serialized values, it'll be writing empty bytes and checking just if storage exists for the given keys. I think keeping the hashing functionality makes sense, to keep key length consistent

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

Successfully merging a pull request may close this issue.

2 participants