Document disable_assert_evaluation theory atttribute in the manual
ci/woodpecker/push/build Pipeline was successful Details

This commit is contained in:
Nicolas Méric 2023-05-24 14:17:16 +02:00
parent 2c0b51779e
commit 4f8e588138
2 changed files with 7 additions and 1 deletions

View File

@ -232,7 +232,8 @@ assert* [resultProof3::result, evidence = "proof", property="[@{thm \<open>HOL.s
\<open>evidence @{result \<open>resultProof3\<close>} = evidence @{result \<open>resultProof2\<close>}\<close>
text\<open>
Evaluation of \<open>assert*\<close> can be disabled using the *\<open>disable_assert_evaluation\<close> theory attribute.
The evaluation of @{command "assert*"} can be disabled
using the *\<open>disable_assert_evaluation\<close> theory attribute.
Then only the checking of the term is done:
\<close>
declare[[disable_assert_evaluation]]

View File

@ -520,6 +520,11 @@ The @{command "assert*"}-command allows for logical statements to be checked in
% TODO:
% Section reference @{docitem (unchecked) \<open>text-elements-expls\<close>} has not the right number
This is particularly useful to explore formal definitions wrt. their border cases.
For @{command "assert*"}, the evaluation of the term can be disabled
with the \<^boxed_theory_text>\<open>disable_assert_evaluation\<close> theory attribute:
@{boxed_theory_text [display]\<open>
declare[[disable_assert_evaluation]]\<close>}
Then @{command "assert*"} will act like @{command "term*"}.
The @{command "definition*"}-command allows \<open>prop\<close>, \<open>spec_prems\<close>, and \<open>for_fixes\<close>
(see the @{command "definition"} command in @{cite "wenzel:isabelle-isar:2020"}) to contain