-
Notifications
You must be signed in to change notification settings - Fork 44
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
Bug in ThreeValuedEquivalenceRelation#projectToConstraintsWith #234
Comments
I'd like to add that if some adds a method to a class he or she should add an author tag. I did nothing with |
I agree with @Heizmann that the method leads to sharing of an underlying Set between two ThreeValuedEquivalenceRelations, which is clearly unintended. (The intended purpose is to keep all constraints where at least one side is in the given Set elems) Can I delete the projectTo method after fixing projectToConstraintsWith? Eclipse shows me it is not referenced, but it has been wrong before.. |
actually, I now believe it was not a bug -- at least the underlying sets were not shared. |
No. I need this method and it was not nice to comment the code. |
It would be good if you could also update the documentation. If one can understand the documentation it might also become clear what your method does. |
sorry. I updated both documentation and method name (commits linked above in this thread), dont you like them? |
I did no knew that you also updated the documentation. |
While constructing seemingly a copy the above mentioned method in fact reuses data structure of the original.
I cannot understand its documentation but I guess the problem is a bug.
I did not want to change the original method (currently used in an evaluation) and added a new method ThreeValuedEquivalenceRelation#projectTo
68916df
Please check and delete the old method in case the new method fixes the problem.
The text was updated successfully, but these errors were encountered: