[FIX] Fix variables equality and hashes #4957
Merged
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.
Issue
Fixes (partially or completely) #4870
Problem is the following:
The problem is that
var1
andvar2
have equal hash (also__eq__
returns True). This happens sincevar1
havecompute_value
with identity pointing to the variablea
; variablesa
andvar2
have same hash since they have the same name and samecompute_value
(None
).The Domain has a dictionary with index for each variable. Variables are keys in dict, when updating dictionary index is set for variable
Cluster x
instead ofCluster
(same hashes).Description of changes
Variables are not equal if their names are not equal and their hashes are not equal either. This avoids problems in the domain (two vars with same hash).
Includes