package coq-lsp
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=1a0639b7774a79c8489b3e7e1ea606a24c857dc70833bbafb79b6d620c18b2b1
sha512=32782243b628fc8a92100778816772baf304335f35518e330c6c4a1b22b2139e255610f2091b47def590877455d361e22beab8ecc4f06b3f13da4e75a576fa07
doc/coq-lsp.petanque/Petanque/Agent/index.html
Module Petanque.Agent
Source
Protocol notes:
The idea is that the types of the functions here have a direct translation to the JSON-RPC (or any other) protocol.
Thus, types here correspond to types in the wire, except for cases where the protocol layer performs an implicit mapping on types.
So far, the mappings are:
uri
<->Doc.t
int
<->State.t
The State.t
mapping is easy to do at the protocol level with a simple mapping, however uri -> Doc.t
may need to yield to the document manager to build the corresponding doc
. This is very convenient for users, but introduces a little bit more machinery.
We could imagine a future where State.t
need to be managed asynchronously, then the same approach that we use for Doc.t
could happen.
val start :
token:Coq.Limits.Token.t ->
doc:Fleche.Doc.t ->
?opts:Run_opts.t ->
?pre_commands:string ->
thm:string ->
unit ->
State.t Run_result.t R.t
start ~token ~doc ~pre_commands ~thm
start a new proof for theorem thm
in file uri
under fn
. token
can be used to interrupt the computation. Returns the proof state or error otherwise. pre_commands
is a string of dot-separated Coq commands that will be executed before the proof starts.
val run :
token:Coq.Limits.Token.t ->
?opts:Run_opts.t ->
st:State.t ->
tac:string ->
unit ->
State.t Run_result.t R.t
run ~token ?memo ~st ~tac
tries to run tac
over state st
. memo
(by default true) controls whether the command execution will be memoized in Flèche incremental engine.
goals ~token ~st
return the list of goals for a given st
Return the list of defined constants and inductives for a given state. For now we just return their fully qualified name, but more options are of course possible.