| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |\
| |
| |
| | |
points of Camlp5
|
| | | |
|
| |/
|
|
| |
This allows to append /archive at the end.
|
| |\
| |
| |
| | |
constr in Constr
|
| | | |
|
| |/ |
|
| |\ |
|
| |\ \
| | |
| | |
| | | |
constants
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
|/| |
|
| |\ \ |
|
| | |/
| |
| |
| | |
This reverts commit 3a44a190a7f5d057b6a4bcb50124b42d83f3d03d.
|
| |/
|
|
| |
See https://github.com/Karmaki/coq-dpdgraph/issues/50 for context
|
| |\ |
|
| | | |
|
| |/ |
|
| |\ |
|
| |\ \
| | |
| | |
| | | |
to anomaly)
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We had mostly used absolute links in the past.
I just discovered that GitHub recommends using relative links instead:
https://help.github.com/articles/basic-writing-and-formatting-syntax/#relative-links
and indeed my Emacs Markdown mode can handle relative links but doesn't
interpret absolute links relatively to the root of the git repository.
[ci skip]
|
| | |/
|/|
| |
| | |
To be removed in 8.10.
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Packages such as `menhir` or `elpi` are fragile w.r.t. updates, so
allowing a non-deterministic install in the Dockefile seems risky. We
have found trouble with Menhir in the past. We thus specify a concrete
version for all `CI_OPAM` packages.
cc: https://github.com/AbsInt/CompCert/issues/234
We also add remove `hevea` from `apt` dependencies as it hasn't been
needed since #7466 and add `texlive-science` which is needed to build
the `source-doc` target due to the `textgreek` package being used.
|
| |/ / |
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
https://github.com/AbsInt/CompCert/issues/234
|
| |\ \ \ |
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| |\ \ \ \ |
|
| | |_|/ /
|/| | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is needed for CI packages that use `META.coq` such as in
https://github.com/coq/coq/pull/7656 .
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
We bump Windows builds to 4.06.1, IMHO it makes sense to use the
latest OCaml version to build on that platform due to the support
status and number of fixes.
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We make the vernacular implementation self-contained in the `vernac/`
directory. To this extent we relocate the parser, printer, and AST to
the `vernac/` directory, and move a couple of hint-related types to
`Hints`, where they do indeed belong.
IMO this makes the code easier to understand, and provides a better
modularity of the codebase as now all things under `tactics` have 0
knowledge about vernaculars.
The vernacular extension machinery has also been moved to `vernac/`,
this will help when #6171 [proof state cleanup] is completed along
with a stronger typing for vernacular interpretation that can
distinguish different types of effects vernacular commands can perform.
This PR introduces some very minor source-level incompatibilities due
to a different module layering [thus deprecating is not
possible]. Impact should be relatively minor.
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We remove the `fix N / cofix N` forms from the tactic language. This
way, these tactics don't depend anymore on the proof context, in
particular on the proof name, which seems like a fragile practice.
Apart from the concerns wrt maintenability of proof scripts, this also
helps making the "proof state" functional; as we don't have to
propagate the proof name to the tactic layer.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
comments.
[ci skip]
|
| | | |
| | |
| | |
| | | |
[ci skip]
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Clarification prompted by Jim Fehrle.
[ci skip]
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `ide` folder contains two different binaries, the language server
`coqidetop` and `coqide` itself.
Even if these binaries are in the same folder, the only thing they
have in common is that they link to the protocol files. In the OCaml
world, having "doubly" linked files in the same project is considered
a bit of an ugly practice, and some build tools such as Dune disallow it.q
Thus, to clean up the build, we move the common protocol files to its
own library `ideprotocol`.
This helps towards Dune integration and towards having an IDE
standalone target, such as the one that was implemented here:
https://github.com/ejgallego/coqide-exp
|
| | |
| |
| |
| |
| |
| | |
This should hopefully alleviate memory problems on gitlab, by first
building the `lite` targets, and then building the remaining
not-that-big targets.
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We turn coqtop "plugins" into standalone executables, which will be
installed in `COQBIN` and located using the standard `PATH`
mechanism. Using dynamic linking for `coqtop` customization didn't
make a lot of sense, given that only one of such "plugins" could be
loaded at a time. This cleans up some code and solves two problems:
- `coqtop` needing to locate plugins,
- dependency issues as plugins in `stm` depended on files in `toplevel`.
In order to implement this, we do some minor cleanup of the toplevel
API, making it functional, and implement uniform build rules. In
particular:
- `stm` and `toplevel` have become library-only directories,
- a new directory, `topbin`, contains the new executables,
- 4 new binaries have been introduced, for coqide and the stm.
- we provide a common and cleaned up way to locate toplevels.
|
| | | |
| | |
| | |
| | | |
We call configure to properly regenerate the Makefile and its dependencies.
|
Matthieu Sozeau
Emilio Jesus Gallego Arias
Pierre-Marie Pédrot
Théo Zimmermann
Maxime Dénès
Andres Erbsen
Hugo Herbelin
Gaëtan Gilbert
Enrico Tassi
Matthieu Sozeau
Michael Soegtrop
Leonidas Lampropoulos
Jason Gross