Something went wrong. Try again.
forked from coq/coq
Something went wrong. Try again.
Rework treatment of default transparency of obligations
By default obligations defined by tactics are defined transparently or opaque according to the Obligations Transparent flag, except proofs of subset obligations which are treated as opaque by default. When the user proves the obligation using Qed or Defined, this information takes precedence, and only when the obligation cannot be Qed'ed because it contains references to a recursive function an error is raised (this prevents the guardness checker error). Shrinked obligations were not doings this correctly. Forcing transparency due to fixpoint prototypes takes precedence over the user preference. Program: do not force opacity of subset proofs, maintaining compatibility.
Author Matthieu Sozeau Date (Jun 27, 2016, 9:29 PM UTC) Commit
Copy SHA
Parent fb4ccbf4 fb4ccbf4a7b66cc7af8b24e00fb19a0b49c769d1