-
Notifications
You must be signed in to change notification settings - Fork 94
Indexing performance + lazy dense dicts #1140
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
Conversation
# Conflicts: # src/Utilities/cachingoptimizer.jl # src/Utilities/dense_dict.jl
I remember we hesitated between adding a dict in DenseDict or using DenseDict inside a CleverDict to switch from DenseDict to Dict in case of deletion. I thought we decided the second one but I don't remember the details |
I think we should
|
I think we only hesitated because it could be too similar to CleverDict. |
We need to be careful with CleverDict because of the downstream usage. |
one problem is that:
As methods to be overloaded, while DenseDicts get |
We could use these functions as default for the map and inverse map of DenseDict so that it is non-breaking |
It is a bit confusing that we have so many types of dictionaries. It's probably okay to get some performance improvement for now, but at some point I'd like to go through and tidy up a lot of this. |
So instead of adding a DenseDict inside CleverDict I will merge the two of them. |
Merging them sounds good |
Follows: #1129
This avoids the conversion from dense dict to standard dict in copy functions.