Closed palmskog closed 6 years ago
The current plan is to deprecate coq-fcsl-pcm
at some point and release the full coq-fcsl
library which will include coq-fcsl-pcm
.
So if I port something to this library now, I will have to re-port it again to the full coq-fcsl
in the near future? Can you give some indication of how much things will change going from coq-fcsl-pcm
to coq-fcsl
?
We are only planning to add more stuff, like more instances of pcm
structure, morphisms between PCMs, some examples of verification of concurrent algorithms. So coq-fcsl-pcm
is essentially a stripped down version of the future coq-fcsl
library, but that one will be released only in the second half of this year.
OK, that sounds reasonable as long as the core definitions don't undergo radical changes. Here's an example of what it took to port one project to coq-fcsl-pcm
from HTT, for reference.
Thanks for sharing this.
I will add your projects to the future coq-fcsl
's CI.
Note that since this development uses the namespace/directory
fcsl
(and not, say,fcslpcm
orfcsl_pcm
), it would conflict with any other (OPAM) package in the future that also uses the namespacefcsl
. For example, if I first installed bothcoq-fcsl-pcm
and the other hypothetical package via OPAM, and then removedcoq-fcsl-pcm
, the other package's files would be removed also. Are you sure this won't be an issue in the future, i.e., that there will be no packaging of other FCSL code?