-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ontop
option seems to be not supported
#202
Comments
The new experimental command `(Fork (fifo_in file) (fifo_out file))` will (hard) fork a new SerAPI process and redirect the input / output towards the given Unix FIFOs. This API is experimental but should allow quite a few advantages to some users willing to perform speculative execution. In particular, it should greatly improve the use case in #202 .
Hi @rashchedrin , indeed this is not supported upstream; unless you are on an "Edit" branch, which we don't really support, I think Coq can only have one document, so you if you have a document:
and you want to do I propose a different solution for you use case, in PR #210 . With that PR, you can actually call How well that will work is unknown, but it could indeed work pretty well. Would you mind testing / reviewing that PR? I can merge it if that will make your testing easier. |
The new experimental command `(Fork (fifo_in file) (fifo_out file))` will (hard) fork a new SerAPI process and redirect the input / output towards the given Unix FIFOs. This API is experimental but should allow quite a few advantages to some users willing to perform speculative execution. In particular, it should greatly improve the use case in #202 .
The new experimental command `(Fork (fifo_in file) (fifo_out file))` will (hard) fork a new SerAPI process and redirect the input / output towards the given Unix FIFOs. This API is experimental but should allow quite a few advantages to some users willing to perform speculative execution. In particular, it should greatly improve the use case in #202 .
Thank you for implementing this! This might be a game changer for me. I'll take a closer look at it after 2-3 days (I need to finish some of my experiments first). |
The new experimental command `(Fork (fifo_in file) (fifo_out file))` will (hard) fork a new SerAPI process and redirect the input / output towards the given Unix FIFOs. This API is experimental but should allow quite a few advantages to some users willing to perform speculative execution. In particular, it should greatly improve the use case in #202 .
Will release the |
CHANGES: * [serapi] (!) Bump public library versioning [breaking change] * [opam] Bump upper bound on ppx_sexp_conv to 0.15, allowing SerAPI to work with the 0.14 set of Jane Street packages. * [serapi] Fix goal printing anomaly (ejgallego/coq-serapi#230, fixes ejgallego/coq-serapi#228 @corwin-of-amber) * [sertop ] New `(Fork (fifo_in file) (fifo_out file))` command, that will (hard) fork a new SerAPI process and redirect the input / output towards the given Unix FIFOs. This API is experimental but should allow quite a few advantages to some users willing to perform speculative execution. (ejgallego/coq-serapi#210 , improves ejgallego/coq-serapi#202 , @ejgallego) - [serapi] Fix missing newline to separate goals (ejgallego/coq-serapi#235, fixes ejgallego/coq-serapi#231, @ejgallego)
CHANGES: * [serapi] (!) Bump public library versioning [breaking change] * [opam] Bump upper bound on ppx_sexp_conv to 0.15, allowing SerAPI to work with the 0.14 set of Jane Street packages. * [serapi] Fix goal printing anomaly (ejgallego/coq-serapi#230, fixes ejgallego/coq-serapi#228 @corwin-of-amber) * [sertop ] New `(Fork (fifo_in file) (fifo_out file))` command, that will (hard) fork a new SerAPI process and redirect the input / output towards the given Unix FIFOs. This API is experimental but should allow quite a few advantages to some users willing to perform speculative execution. (ejgallego/coq-serapi#210 , improves ejgallego/coq-serapi#202 , @ejgallego) - [serapi] Fix missing newline to separate goals (ejgallego/coq-serapi#235, fixes ejgallego/coq-serapi#231, @ejgallego)
I want to work with different proof branches. It seems that option
ontop
ofAdd
command is designed specifically for this use case, however, when I try to use it it says that"Stm.add called for a different state (4) than the tip: 5. This is not supported yet, sorry."
. Here's input to reproduce this message:Here's the complete output of this sequence:
https://gist.github.com/rashchedrin/3584eaa4316dc670947bf5501a031a7b
(I entered them in command prompt of
rlwrap sertop --printer=human
)My version of sertop is 8.11.0+0.11.0 .
The last
(Exec 4)
command doesn't change anything: I've tried with and without it with the same result. I've also tried it with and without --deep-edits flag (I have no idea what it does), result is the same.If there is any workaround for this, please tell me, because utilizing branch switching for faster ATP is the main focus of my work right now.
The text was updated successfully, but these errors were encountered: