-
Notifications
You must be signed in to change notification settings - Fork 99
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
feat: add keys()
and vals()
for AssocList
#646
base: master
Are you sure you want to change the base?
feat: add keys()
and vals()
for AssocList
#646
Conversation
Dear @dpanchenko, In order to potentially merge your code in this open-source repository and therefore proceed with your contribution, we need to have your approval on DFINITY's CLA. If you decide to agree with it, please visit this issue and read the instructions there. Once you have signed it, re-trigger the workflow on this PR to see if your code can be merged. — The DFINITY Foundation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can use List.toIter instead of the entries
function defined here. It is the same code, but just because List.toIter already exists we don't need to provide it a second time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Resolves #581 |
I don't know about the size requirement for keys() and vals(). Does anyone know if it is really O(1)? |
keys()
and vals()
for AssocList
keys()
and vals()
for AssocListkeys()
and vals()
for AssocList
No description provided.