Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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(stdlib): Add lookupCI for assocarray and Node #639
feat(stdlib): Add lookupCI for assocarray and Node #639
Changes from 8 commits
e8ea91d
e148628
44c6f53
29809ef
393c24e
f10202c
d8f2e58
f353bdf
29ea65a
f7d7bba
d8aade1
53bed83
f0a56a7
020bc4a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This seems less than ideal, as it'll cause an
O(n)
lookup for every access oncesetCaseInsensitive
is called. I'm curious if there's an alternative solution we can take that won't require us to iterate across every element every time. Could we maintain a case-insensitiveMap
next to the case-sensitive one, and write to both for everyset()
? It'd of course require twice as much memory, but would maintain constant time lookups.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.
Hey, I even forget about it, a great catch.
So I've taken your idea of using a second map and used it for mapping lower case keys to case sensitive keys. so it will not consume so much memory, will not introduce additional computation and almost saves previous performance.
but there is still be
O(n)
when we delete keys in case sensitive mode, cuz we can delete key that was used as alias inKeysMap
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.
Perhaps I've missed something — why's this variable
lKey
while the rest arekey
?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.
idk why, but it was as is before my changes
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.
fixed