-
Notifications
You must be signed in to change notification settings - Fork 19
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
Update to MetaCoq 1.3 #242
Comments
I already started looking at updating to MetaCoq 1.3. However, I ran into a problem that looks like a MetaCoq bug. I haven't had time yet to identify the exact cause of the problem. |
@4ever2 we should get ConCert in MetaCoq CI... |
Here's what we need to do. Let's find a local Nix expert...
https://coq.zulipchat.com/#narrow/stream/237658-MetaCoq/topic/CI/near/292131799
…On Tue, Apr 9, 2024 at 9:17 AM 4ever2 ***@***.***> wrote:
I already started looking at updating to MetaCoq 1.3. However, I ran into
a problem that looks like a MetaCoq bug. I haven't had time yet to identify
the exact cause of the problem.
—
Reply to this email directly, view it on GitHub
<#242 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABTNTWJTB7EYBW2QDIDETTY4OI2FAVCNFSM6AAAAABF54QKOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBUGMYDCOBTGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@4ever2 It seems you have a version that works with MC 1.3 (without support for the elm extraction, that's no big deal of course). |
I have a version of ConCert now (with a bunch of things commented out), that compiles with MetaCoq 1.3. Extracting the Running
It seems I need version 2.0.0, which is not available via crates.io, is that what you currently use? |
@womeier I seem to recall you made progress on this. What's the current status? |
I commented out some proofs and tests, to make the counter module extraction work with MetaCoq 1.3, I don't think the other smart contracts work. These are my changes: |
I was looking into extracting the counter module to concordium, using our Wasm backend for CertiCoq.
CertiCoq is currently on MetaCoq 1.3, which ConCert doesn't seem to work with.
Do you already have plans to update?
The text was updated successfully, but these errors were encountered: