You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In contrast to Object.equals(Object) it is not necessarily transitive. This is because it is reflexive, but not necessarily symmetric. This means that when x.equivTo(y) == true and y.equivTo(z) == true, this does not imply x.equivTo(z) == true. A trivial example showing this is when x refers to the same object as z, since equivTo is not always symmetric.
However, this reasoning does not imply lack of transitivity: In P -> Q, the reasoning simply shows that sometimes ~P -> Q, but not that P -> ~Q. Many partial orders are counterexamples to reflexive-transitive relations not being symmetric.
Version
Latest develop branch
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
What happened?
https://soot-oss.github.io/SootUp/apidocs/sootup/core/jimple/basic/JimpleComparator.html
In this documentation, the following is stated:
However, this reasoning does not imply lack of transitivity: In P -> Q, the reasoning simply shows that sometimes ~P -> Q, but not that P -> ~Q. Many partial orders are counterexamples to reflexive-transitive relations not being symmetric.
Version
Latest develop branch
Relevant log output
No response
The text was updated successfully, but these errors were encountered: