I just found out that the stm takes its own command line arguments https://github.com/coq/coq/blob/92b9d3ca9928e8332ac81175272e8e4489961d71/stm/stmargs.ml
Michael's message confused me because I recently updated the help screen for CoqIDE and I don't remember seeing the async stuff.
So CoqIDE has a -coqtop-flags
flag for passing options to the subprocess. Does VSCoq have something similar?
@Michael Soegtrop VsCoq just passes -async-proofs on
, I didn't know about this -j
option. But do we just need to add a setting and slap the option in?
@Ali Caglayan : it might be that it was removed from the docs because it was quite unstable for a long time (at least on Windows due to a bug in GtkSourceView which killed global data structures on each thread kill).
Hmm, time to try "Coqtop: Args" by hand first...
@Paolo Giarrusso : I guess so, but Enrico is the expert.
Where would I put "Coqtop: Args"? In _CoqProject?
I think in vscoq's config right?
yes, I just added "coqtop.args": ["-async-proofs-j", "10"]
to settings.json
, and it passes a smoke test
Cool - I will try it right away ... (after I finished the test suggested by Guillaume with CoqIDE 8.12..8.15 and VsCoq).
and you'll have to make sure to restart coqidetop
to confirm
I've split this thread to make the original a bit less cluttered
Coq: Reset
(often?) doesn't restart the process, so my usual options killall coqidetop.opt
, or Cmd-Shift-P
"Developer: Reload Window".
I also do the reload window workaround
I guess I will just restart VsCode ...
the latter's cool because it keeps even unsaved file contents :-D
One of the reasons I don't like using VSCoq for other stuff
Paolo Giarrusso said:
yes, I just added
"coqtop.args": ["-async-proofs-j", "10"]
tosettings.json
, and it passes a smoke test
I tested this and indeed I get the expected speed up. Very nice! I would suggest to add an explicit "threads" option to the UI settings.
It is interesting that this very nice feature apparently ended up in oblivion - I guess cause of the initial stability issues. For me the parallel proof feature really saves quite a bit of time.
So right now for me (that is from the very subjective view point of my work) the only reason for using CoqIDE is the Ltac debugger, but I don't use it that regularly, so I will probably stick with VsCoq.
Thanks a lot for the feedback, Michael! Do not hesitate to open an issue on the VsCoq repo for the threads configurability improvement.
I created issue (https://github.com/coq-community/vscoq/issues/284).
I totally agree we should have an option :-)
and it's easy enough that I'm on it :-)
I don't really know what I'm doing, but things like this seem easy to add, also thanks to VSCode's IDE support: https://github.com/coq-community/vscoq/pull/285
Last updated: Oct 13 2024 at 01:02 UTC