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
I believe consensus was around [Equivalence is tested with the `Term.equals()` function instead of `===` or `==`.](#160 (comment)) but I had not stuck it in the PR.
Copy file name to clipboardExpand all lines: index.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -100,7 +100,7 @@ <h2>Design elements and principles</h2>
100
100
<li>Interfaces do <em>not</em> specify how instances are stored in memory.</li>
101
101
<li>Interfaces mandate specific pre-defined methods such as <code>.equals()</code>.</li>
102
102
<li>
103
-
Interfaces are not expected to expose internal objects or return the same object from sucessive calls. Callers shoud use the `Term.equals()` function instead of `===` or `==` to test for equivalence.
103
+
Interfaces are not expected to expose internal objects or return the same object from sucessive calls. Equivalence is tested with the `Term.equals()` function instead of `===` or `==`.
104
104
</li>
105
105
<li>
106
106
Factory functions (e.g., <code>quad()</code>) or methods (e.g.,
0 commit comments