Ralf Jung (14c692e3) at 26 Mar 16:59
Automatic publication of dev.2024-03-26.0.119a9fa1 for coq-diaframe...
Ralf Jung (105a791f) at 25 Mar 13:57
Automatic publication of dev.2024-03-25.0.ec56b868 for coq-diaframe...
Ralf Jung (77144a01) at 24 Mar 10:42
Automatic publication of dev.2024-03-24.0.41042d04 for coq-actris
The leaf paper has this:
(Coq formalization here.)
Amin suggested something similar a long time ago.
Not sure which formulation works best, but we should have something like that. :)
Whatever the rule is, it should be strong enough to prove things like
Lemma pointsto_and_sep (l1 l2:loc) (v1 v2:val) :
l1 ≠ l2 ->
l1 ↦ v1 ∧ l2 ↦ v2 -∗
l1 ↦ v1 ∗ l2 ↦ v2.
Lemma pointsto_and_eq l x y :
l ↦ x ∧ l ↦ y -∗ ⌜x = y⌝
Ralf Jung (009b5c58) at 22 Mar 15:19
Automatic publication of dev.2024-03-22.0.2c385241 for coq-gpfsl co...
Ralf Jung (2c385241) at 22 Mar 14:57
bump Iris
Timing results will appear at:
FWIW here's a list of all eval cbv
in the repo before this MR:
iris/proofmode/ltac_tactics.v
157: | [] => eval cbv in Hs
413: let Hs := eval cbv in (env_dom (env_intuitionistic Δ)) in go Hs
422: let Hs := eval cbv in (env_dom (env_spatial Δ)) in go Hs
888: let Hs' := eval cbv in (if lr then Hs else Hs_frame ++ Hs) in
1019: let b := eval cbv [use_tac_specialize_intuitionistic_helper] in
iris/proofmode/ident_name.v
12: eval cbv in (ltac:(clear; intros id; assumption) : unit → unit).
iris/proofmode/intro_patterns.v
182: | intro_pat => eval cbv in (intro_pat_intuitionistic p)
183: | list intro_pat => eval cbv in (forallb intro_pat_intuitionistic p)
186: eval cbv in (forallb intro_pat_intuitionistic pat)
Yeah that spam system is very overeager. :/ I have told the spam system to "trust" you and submitted your messages as ham.
Ralf Jung (24764b95) at 19 Mar 07:25
Automatic publication of dev.2024-03-19.0.9b4483ea for coq-actris
LGTM -- @robbertkrebbers any final remarks?
@msammler can you add a changelog entry?
Yeah that sounds like things should still work as intended.
Sorry, I didn't intend to insult anyone. I was already expecting the Coq-platform issue as they have been working with us for a while already. My understanding is that they have some automatic tooling so it's easier for them if we can keep their issue open. I don't know if you have such a tooling as well.
Sorry for any inconveniences this may cause.
I saw you had commits for Coq 8.19 support, but didn't tag a release yet.
I'm working on updating the Coq ecosystem in Debian with Coq 8.19, so I'd like an official release.
There's no hurry: there's a handful of packages still blocking anyway. This issue will help me track the progress.
Thanks,
Closing in favor of #206 (which the platform folks are tracking so I'd rather close this one than that one)
The Coq team released Coq 8.19.0
on January 24th, 2024.
The corresponding Coq Platform release 2024.01
should be released before April 30th, 2024.
It can be delayed in case of difficulties until May 15th, 2024, but this should be an exception.
This issue is to inform you that to our (possibly a few days old) best knowledge the latest released version of your project (4.1.0) does not work with Coq 8.19.0
.
We tried to remove version restrictions in opam files and possibly make or configure files, but this did not suffice.
Please note that in Coq Platform CI (unlike Coq CI) we test only released / tagged versions. Coq CI appears to test this project, but has some special handling for your project which makes it difficult to retrieve the commit it tests for your project.
Could you please create a tag and opam package, or communicate us any existing tag that works with Coq branch v8.19, preferably before March 31st, 2024? In case we might have to delay the Coq Platform release cause of issues with your project, we would prefer to be informed about the situation as early as possible.
In case the tag and opam package are available before March 31st, 2024, it will be included in an early Coq Platform beta release of the for Coq 8.19.0.
The working branch of Coq Platform, can be found here main.
It contains package pick ~8.19~2024.01+beta1
which already supports Coq version 8.19.0
and contains already working (possibly patched / commit pinned) Coq Platform packages.
Please don't close this issue, even after creating the new tag and/or opam package. We will close the issue after updating Coq Platform. This is a measure of 'double book keeping' in order to avoid that we ship the wrong version.
In any case, Coq Platform won't be released before this issue is closed!
Thanks!
P.S.: this issue has been created automatically based on CI status.