package coq-core
The Coq Proof Assistant -- Core Binaries and Tools
Install
Dune Dependency
Authors
Maintainers
Sources
coq-8.18.0.tar.gz
md5=8d852367b54f095d9fbabd000304d450
sha512=46922d5f2eb6802a148a52fd3e7f0be8370c93e7bc33cee05cf4a2044290845b10ccddbaa306f29c808e7c5019700763e37e45ff6deb507b874a4348010fed50
doc/coq-core.vernac/RetrieveObl/index.html
Module RetrieveOblSource
Source
type obligation_info =
(Names.Id.t
* Constr.types
* Evar_kinds.t Loc.located
* (bool * Evar_kinds.obligation_definition_status)
* Int.Set.t
* unit Proofview.tactic option)
arrayident, type, location of the original evar, (opaque or transparent, expand or define), dependencies as indexes into the array, tactic to solve it
Source
val retrieve_obligations :
Environ.env ->
Names.Id.t ->
Evd.evar_map ->
int ->
?deps:Evar.Set.t ->
?status:Evar_kinds.obligation_definition_status ->
EConstr.t ->
EConstr.types ->
obligation_info
* ((Evar.t * Names.Id.t) list
* ((Names.Id.t -> EConstr.t) ->
EConstr.t ->
Constr.t))
* Constr.t
* Constr.tretrieve_obligations env id sigma fs ?status body type returns obls, (evnames, evmap), nbody, ntype a list of obligations built from evars in body, type.
fs is the number of function prototypes to try to clear from evars contexts. evnames, evmap is the list of names / substitution functions used to program with holes. This is not used in Coq, but in the equations plugin; evnames is actually redundant with the information contained in obls