Implement {:nowarn}, clarify some messages, and add a few tests

1 files changed, 25 insertions, 25 deletions

diff --git a/Test/triggers/loop-detection-messages--unit-tests.dfy.expect b/Test/triggers/loop-detection-messages--unit-tests.dfy.expect
index 804a0116..eba8c179 100644
--- a/Test/triggers/loop-detection-messages--unit-tests.dfy.expect
+++ b/Test/triggers/loop-detection-messages--unit-tests.dfy.expect
@@ -1,37 +1,37 @@
 loop-detection-messages--unit-tests.dfy(11,9): Info: Selected triggers: {f(f(i))}

- Rejected triggers: {f(i)} (may loop with {f(f(i))})

-loop-detection-messages--unit-tests.dfy(12,9): Warning: Selected triggers: {f(i)} (may loop with {f(i + 1)})

- (!) Suppressing loops would leave this expression without triggers.

-loop-detection-messages--unit-tests.dfy(13,9): Info: Selected triggers: {f(i)} (may loop with {f(i + 1)})

-loop-detection-messages--unit-tests.dfy(15,9): Info: For expression {false ==> f(i) == f(i + 1)}:

+ Rejected triggers: {f(i)} (may loop with "f(f(i))")

+loop-detection-messages--unit-tests.dfy(12,9): Warning: Selected triggers: {f(i)} (may loop with "f(i + 1)")

+ /!\ Suppressing loops would leave this expression without triggers.

+loop-detection-messages--unit-tests.dfy(13,9): Info: Selected triggers: {f(i)} (may loop with "f(i + 1)")

+loop-detection-messages--unit-tests.dfy(15,9): Info: For expression "false ==> f(i) == f(i + 1)":

    Selected triggers: {g(i)}

-   Rejected triggers: {f(i)} (may loop with {f(i + 1)})

-loop-detection-messages--unit-tests.dfy(15,9): Info: For expression {false ==> f(i) == g(i)}:

+   Rejected triggers: {f(i)} (may loop with "f(i + 1)")

+loop-detection-messages--unit-tests.dfy(15,9): Info: For expression "false ==> f(i) == g(i)":

    Selected triggers:

      {g(i)}, {f(i)}

-loop-detection-messages--unit-tests.dfy(16,9): Warning: For expression {false ==> f(i) == f(i + 1)}:

-   Selected triggers: {f(i)} (may loop with {f(i + 1)})

-   (!) Suppressing loops would leave this expression without triggers.

-loop-detection-messages--unit-tests.dfy(16,9): Info: For expression {false ==> f(i) == f(i)}:

+loop-detection-messages--unit-tests.dfy(16,9): Warning: For expression "false ==> f(i) == f(i + 1)":

+   Selected triggers: {f(i)} (may loop with "f(i + 1)")

+   /!\ Suppressing loops would leave this expression without triggers.

+loop-detection-messages--unit-tests.dfy(16,9): Info: For expression "false ==> f(i) == f(i)":

    Selected triggers: {f(i)}

-loop-detection-messages--unit-tests.dfy(17,9): Info: For expression {false ==> f(i) == f(i + 1)}:

-   Selected triggers: {f(i)} (may loop with {f(i + 1)})

-loop-detection-messages--unit-tests.dfy(17,9): Info: For expression {false ==> f(i) == f(i)}:

+loop-detection-messages--unit-tests.dfy(17,9): Info: For expression "false ==> f(i) == f(i + 1)":

+   Selected triggers: {f(i)} (may loop with "f(i + 1)")

+loop-detection-messages--unit-tests.dfy(17,9): Info: For expression "false ==> f(i) == f(i)":

    Selected triggers: {f(i)}

 loop-detection-messages--unit-tests.dfy(19,9): Info: Selected triggers: {f(i)}

-loop-detection-messages--unit-tests.dfy(20,9): Warning: (!) No terms found to trigger on.

-loop-detection-messages--unit-tests.dfy(21,9): Info: Not generating triggers for {false ==> f(i + 1) == 0}.

+loop-detection-messages--unit-tests.dfy(20,9): Warning: /!\ No terms found to trigger on.

+loop-detection-messages--unit-tests.dfy(21,9): Info: Not generating triggers for "false ==> f(i + 1) == 0". Note that {:autotriggers false} can cause instabilities. Consider using {:nowarn}, {:matchingloop} (not great either), or a manual trigger instead.

 loop-detection-messages--unit-tests.dfy(23,9): Info: Selected triggers: {f(j), f(i)}

-loop-detection-messages--unit-tests.dfy(24,9): Warning: (!) No trigger covering all quantified variables found.

-loop-detection-messages--unit-tests.dfy(25,9): Info: For expression {false ==> f(i) == f(i)}:

+loop-detection-messages--unit-tests.dfy(24,9): Warning: /!\ No trigger covering all quantified variables found.

+loop-detection-messages--unit-tests.dfy(25,9): Info: For expression "false ==> f(i) == f(i)":

    Selected triggers: {g(j), f(i)}

-loop-detection-messages--unit-tests.dfy(25,9): Info: For expression {false ==> g(j) == 0}:

+loop-detection-messages--unit-tests.dfy(25,9): Info: For expression "false ==> g(j) == 0":

    Selected triggers: {g(j), f(i)}

-loop-detection-messages--unit-tests.dfy(26,9): Warning: For expression {false ==> f(i) == f(i)}:

-   (!) No trigger covering all quantified variables found.

-loop-detection-messages--unit-tests.dfy(26,9): Warning: For expression {false ==> g(j + 1) == 0}:

-   (!) No trigger covering all quantified variables found.

-loop-detection-messages--unit-tests.dfy(27,9): Info: Not generating triggers for {false ==> f(i) == f(i)}.

-loop-detection-messages--unit-tests.dfy(28,9): Info: Not generating triggers for {false ==> f(i) == f(i)}.

+loop-detection-messages--unit-tests.dfy(26,9): Warning: For expression "false ==> f(i) == f(i)":

+   /!\ No trigger covering all quantified variables found.

+loop-detection-messages--unit-tests.dfy(26,9): Warning: For expression "false ==> g(j + 1) == 0":

+   /!\ No trigger covering all quantified variables found.

+loop-detection-messages--unit-tests.dfy(27,9): Info: Not generating triggers for "false ==> f(i) == f(i)". Note that {:autotriggers false} can cause instabilities. Consider using {:nowarn}, {:matchingloop} (not great either), or a manual trigger instead.

+loop-detection-messages--unit-tests.dfy(28,9): Info: Not generating triggers for "false ==> f(i) == f(i)".

 

 Dafny program verifier finished with 4 verified, 0 errors