GitLab

Call_provers:

- drop closures "pre_prover_call" and "post_prover_call". They were
  intended to be used for synchronous interaction with provers from
  multiple threads. This is now responsibility of the proof server:
  (a) any Call_prover.call_on_[file|buffer] submits the proof task
      immediately to the server;
  (b) all proof results are handled in the working Why3 thread.

- Call_provers.query_call returns a tri-state "prover_update" type
  which can be one of: "ProverStarted" (returned after the proof
  server informs Why3 that a prover was started), "ProverFinished"
  (returned after the proof server returns the prover result), and
  "NoUpdates" (returned when the proof server has not sent any new
  updates concerning the proof task in question).

    IMPORTANT: query_call does not maintain the state of a given
  prover call. In a normal use case, "ProverFinished" is returned
  _exactly_ once, and "ProverStarted" _at_most_ once (never for
  an editor call or when rapidly overwritten by "ProverFinished").

    TODO: extend the proof server protocol and implementation to
  send "ProverStarted" events back to Why3.

TODO: Coq-related failures

  bitvectors/power2
  bellman_ford
  vstte12_combinators
  hoare_logic/blocking_semantics5

still problematic:

  tests-provers/div
  tests-provers/div_real
  check-builtin/int
  bts/fsetint
  logic/bitvectors
  logic/einstein
  logic/genealogy
  bitvectors/power2
  bellman_ford
  knuth_prime_numbers
  vstte12_combinators
  hoare_logic/blocking_semantics5

known issues:
- Timeout is not always recognized
- why3 tactic does not work: ENOENT on connect()
- temporary output files are created in the curdir
- temporary output files are sometimes not erased
- socket file is created in the curdir

New example in progres : Koda Ruskey (functional correctness done; missing proof of correctness for the number of forest colorings)

in particular, every variable defined in
the ghost context is automatically ghost