Stream: jsCoq

Topic: v0.12.1


view this post on Zulip Shachar Itzhaky (Nov 16 2020 at 21:20):

@Emilio Jesús Gallego Arias I think we are ready to announce 0.12.1, WDYT?

view this post on Zulip Emilio Jesús Gallego Arias (Nov 16 2020 at 22:43):

Yes I think so, amazing work!

view this post on Zulip Emilio Jesús Gallego Arias (Nov 16 2020 at 22:44):

I'm still quite busy with the build system / doc manager upstream, sorry I am not very helpful these days

view this post on Zulip Shachar Itzhaky (Nov 17 2020 at 19:10):

Wait there's Coq 8.12.1 already? I missed that fact. So 0.12.1 is still Coq 8.12.0, but we never promised to be consistent with minor versions. :face_palm:

view this post on Zulip Emilio Jesús Gallego Arias (Nov 17 2020 at 20:51):

Indeed the versions have been decoupled, so for example you can have jsCoq 0.12 + Coq 8.12.0 or Coq 8.12.1

view this post on Zulip Emilio Jesús Gallego Arias (Nov 17 2020 at 20:51):

At least for minor versions one goal was to indeed be able to configure the Coq version loaded, but we are far.

view this post on Zulip Emilio Jesús Gallego Arias (Nov 17 2020 at 20:51):

Some time ago I did a prototype where you would load two workers with Coq 8.10 and Coq 8.11 and execute a document simultaneously

view this post on Zulip Emilio Jesús Gallego Arias (Nov 17 2020 at 20:52):

so IMHO less coupling is good

view this post on Zulip Emilio Jesús Gallego Arias (Nov 17 2020 at 20:52):

that means tho that builds get a different tag than the source tree, but that is in principle not a problem

view this post on Zulip Emilio Jesús Gallego Arias (Nov 17 2020 at 20:52):

the same happens for example for any OCaml package that depends on another, stuff like dune-build-info does handle that properly


Last updated: Jan 31 2023 at 11:01 UTC