package coq-core
The Coq Proof Assistant -- Core Binaries and Tools
Install
Dune Dependency
Authors
Maintainers
Sources
coq-8.20.0.tar.gz
md5=66e57ea55275903bef74d5bf36fbe0f1
sha512=1a7eac6e2f58724a3f9d68bbb321e4cfe963ba1a5551b9b011db4b3f559c79be433d810ff262593d753770ee41ea68fbd6a60daa1e2319ea00dff64c8851d70b
doc/coq-core.vernac/RetrieveObl/index.html
Module RetrieveObl
Source
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)
array
ident, 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 * obligation_name_lifter)
* Constr.t
* Constr.t
retrieve_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
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>