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
Copy file name to clipboardExpand all lines: booster/test/rpc-integration/test-issue4118-indexing/README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ This demonstrates a bug caused by discarding rules with non-matching index, fixe
6
6
When an unevaluated function `f` is in an indexed position, the index of the term would have a component `TopSymbol f`, and there would not be (cannot be!) any rules with such an index.
7
7
Therefore the only rules tried would be those with index `Anything` (in that component).
8
8
9
-
* If none of these rules can be applied (which is likely in practice), the returned result is `Stuck` instead of `Aborted` (see [`no-evaluators` test result](../test-no-evaluators/)).
9
+
* If none of these rules can be applied (which is likely in practice), the returned result is `Stuck` instead of `Aborted` (see [`test-no-evaluator`result](../test-no-evaluator/)).
10
10
* All rules tried may have lower priority than one which could apply once the function gets evaluated, leading to a wrong result ( demonstrated in this test).
0 commit comments