aboutsummaryrefslogtreecommitdiff
path: root/doc/sphinx
diff options
context:
space:
mode:
authorErik Martin-Dorel2019-04-03 15:39:11 +0200
committerErik Martin-Dorel2019-04-23 20:22:40 +0200
commit36488400952da5e12c8af451b1a936a34b26039d (patch)
treedeaaf8bc97829427bf444c37ba08496874b7c356 /doc/sphinx
parent4bc91ba5654574d156ebf2934a6fb36d31b40ff9 (diff)
[ssr] under: optimization of the tactic for (under eq_bigl => *)
so it acts "more naturally" like (under eq_bigl; [hnf|]); move=> [*|]. Also: replace "by over." in the doc example with "over."
Diffstat (limited to 'doc/sphinx')
-rw-r--r--doc/sphinx/proof-engine/ssreflect-proof-language.rst15
1 files changed, 9 insertions, 6 deletions
diff --git a/doc/sphinx/proof-engine/ssreflect-proof-language.rst b/doc/sphinx/proof-engine/ssreflect-proof-language.rst
index a40dfa486f..4e40df6f94 100644
--- a/doc/sphinx/proof-engine/ssreflect-proof-language.rst
+++ b/doc/sphinx/proof-engine/ssreflect-proof-language.rst
@@ -3733,7 +3733,7 @@ Let us redo the running example in interactive mode.
Lemma example_map l : sumlist (map (fun m => m - m) l) = 0.
under eq_map => m.
rewrite subnn.
- by over.
+ over.
The execution of the Ltac expression:
@@ -3751,8 +3751,9 @@ involves the following steps:
while the other ones correspond to premises of the rewrite rule (such as
``forall n, F1 n = F2 n`` for ``eq_map``).
-3. If so :tacn:`under` executes the corresponding
- intro pattern :n:`@ipat__i` in each goal.
+3. If so :tacn:`under` puts these n goals in head normal form (using
+ the defective form of the tactic :tacn:`move`), then executes
+ the corresponding intro pattern :n:`@ipat__i` in each goal.
4. Then :tacn:`under` checks that the first n subgoals
are (quantified) equalities or double implications between a
@@ -3805,7 +3806,7 @@ The Ltac expression:
can be seen as a shorter form for the following expression:
-:n:`under @term => [ @i_item__1 | … | @i_item__n | ]; [ @tac__1; over | … | @tac__n; over | cbv beta iota ].`
+:n:`(under @term) => [ @i_item__1 | … | @i_item__n | ]; [ @tac__1; over | … | @tac__n; over | cbv beta iota ].`
Notes:
@@ -3822,10 +3823,12 @@ Notes:
preferred.
+ If the ``do`` clause is provided and the intro pattern is omitted,
- then the defeault :token:`i_item` ``*`` is applied to each branch.
+ then the default :token:`i_item` ``*`` is applied to each branch.
E.g., the Ltac expression:
:n:`under @term do [ @tac__1 | … | @tac__n ]` is equivalent to:
- :n:`under @term => [ * | … | * ] do [ @tac__1 | … | @tac__n ].`
+ :n:`under @term => [ * | … | * ] do [ @tac__1 | … | @tac__n ]`
+ (and it can be noted here that the :tacn:`under` tactic performs a
+ ``move.`` before processing the intro patterns ``=> [ * | … | * ]``).
.. example::