-
#### Description of the problem
This is not really an issue with Coq itself, but with its source code. I’m currently looking at the extraction source code, and I’m noticing a lot of physical equali…
-
#### Description of the problem
I'm trying to build Coq for Void Linux, the i686 target. It fails with errors like
```
File "theories/dune", line 1807, characters 1-778:
1807 | (rule
1808 | …
-
## Description of the problem
If an inductive in Coq named `int` is extracted to OCaml in the presence of `ExtrOcamlNatInt`, the resulting type will also be called `int`, and it will be confused wi…
-
#### Description of the problem
The ssrbool module cannot be extracted, which make its use a bit tricky in projects such as MetaCoq:
File "./theories/Extraction.v", line 34, characters 0-41:…
-
In Section 5.5 of https://arxiv.org/pdf/2108.02995.pdf it is asserted:
> ## Partial applications.
>
> Rust requires all functions to be fully applied when called, unlike Coq which supports parti…
-
ocamljava fails with
"Error: Cannot compile goto_table_4081 (Java method is too long: 94429 bytes)"
The function in question is generated by Menhir into Coq, then extracted into OCaml, so I really ha…
-
#### Description of the problem
Extracting the following generates broken OCaml:
```coq
Module Type ty.
Axiom t : Type.
End ty.
Module x
-
@startuml
actor "Data Analyst" as Hero
participant "Current Analytics" as OW
participant "Need for Mastodon Insights" as Call
participant "Mastodon API Docs" as Mentor
participant "API Authentica…
-
Currently we are cheating in the extraction and using state in OCaml to keep track of the random seed. It would be more interesting verification-wise to get rid of this (very effective) hack and inste…
-
#### Description of the problem
I'd like to know if extraction can be made to work with the vos compillation mode,
it seems to do nothing currently.