Invoke an operation on the prover, that is, encode the input argument, send it to the prover and stream the results to the observer of the operation.
Invoke an operation on the prover, that is, encode the input argument, send it to the prover and stream the results to the observer of the operation.
The observer is automatically instantiated with the underlying environment specified when creating the system.
The returned future gets fulfilled when the
observer transitions into either
Success
or
Failure
state.
Any well-formed response, even if it is an "error", is treated as a success. Only ill-formed responses, e.g. due to decoding errors, will mark the future as failed. Custom observers may deviate from this, but it is generally safe to assume that a failed future represents an internal error (e.g. due to a wrong codec), whereas a successful future may contain expected errors (e.g. due to a wrong input argument or a failing proof).
Instruct the prover to shutdown.
Instruct the prover to shutdown.
Includes unchecked cancellation of all running operations by virtue of the system shutting down completely. Pending futures will not be marked as failed.
It is recommended to wait for all pending futures to complete, or call
cancel
on them before shutdown. It is
guaranteed that when the returned future
succeeds, the prover has been shut down.
Calling anything after dispose is undefined. The object should not be used afterwards.
Depending on the implementation details of the environment used to create this system, it may be unneccessary to call this method. In any case, it is good practice to call it.
The execution context used internally for bi-directional communication with the prover.
The execution context used internally for bi-directional communication with the prover.
Guaranteed to be the same execution context as the execution context of the environment used to create this system.
It is fine to use this execution context for other purposes, for example to transform the futures produced by invoking operations.
Since it is marked as implicit
, it can be readily imported and used.
A running instance of a prover.
This class is thread-safe, that is, running multiple operations at the same time is expected and safe.
edu.tum.cs.isabelle.setup.Setup