Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/metaprogramming/ltac2/tutorial_ltac2_for_ltac1_users.v
Original file line number Diff line number Diff line change
Expand Up @@ -258,8 +258,8 @@ Qed.
(** In Ltac2, this is now written with the syntax [tac1 > [tac21 | tac22]] in order
to avoid confusion between chaining tactics and dispatching.
The latter is asymetric and does not compose opposite to [;].
Moreover, [tac1; tac2; [tac31 | tac32]]
is now parsed as [tac1; (tac2; [tac31 | tac32])] as Ltac2 no longer
Moreover, [tac1; tac2 > [tac31 | tac32]]
is now parsed as [tac1; (tac2 > [tac31 | tac32])] as Ltac2 no longer
automatically delays tactic execution.

Consequently, if [tac1] generates multiple goals, the dispatcher will
Expand Down Expand Up @@ -947,7 +947,7 @@ Ltac2 rec my_first0 tacs :=

(** To write a notation for it, we write:

- ["my_first"] and ["["] / ["]"] are literal keywords that the parser matches
- ["my_first"] and "[" / "]" are literal keywords that the parser matches
verbatim; so that [my_first [...]] is unambiguous

- [tacs] is the name bound in the body to the parsed argument
Expand Down
Loading