| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
Lintian found some spelling errors in the Debian packaging for coq. Fix
them most places they appear in the current source. (Don't change
documentation anchor names, as that would invalidate external
deeplinks.)
This also fixes a bug in coqdoc: prior to this commit, coqdoc would
highlight `instanciate` but not `instantiate`.
|
|\ |
|
|\ \ |
|
|\ \ \
| | | |
| | | |
| | | | |
case of missing record field
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
IIUC, this was a hack to make `Set SsrHave NoTCResolution` behave like
`Global Set SsrHave NoTCResolution`. I don't think it is needed (just
let the user write the desired locality), but if it is, the right way of
doing it is to let clients of Goptions specify a default locality.
|
|\ \ \ |
|
|\ \ \ \ |
|
|\ \ \ \ \ |
|
| |/ / / /
|/| | | |
| | | | |
| | | | | |
As stated in the manual, the fourier tactic is subsumed by lra.
|
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
While we were adding a new field into `QuestionMark`, we
decided to go ahead and refactor the constructor to hold
an actual record. This record now holds the name, obligations, and
whether the evar represents a missing record field.
This is used to provide better error messages on missing record
fields.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes #8067. This is becoming the default in many developments, so it
makes sense to require it too, both for Coq and for Plugins.
|
|/ / /
| | |
| | |
| | | |
Catched by compiling the ml files from ml4.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For now we only copy the templates, but we could do more fancy stuff.
This helps to be compatible with build systems that take care of these
files automatically, see:
https://github.com/coq/coq/pull/6857#discussion_r202096579
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We make it possible to deprecate tactics defined by `Ltac`, `Tactic
Notation` or ML.
For the first two variants, we anticipate the syntax of attributes:
`#[deprecated(since = "XX", note = "YY")]`
In ML, the syntax is:
```
let reflexivity_depr =
let open CWarnings in
{ since = "8.5"; note = "Use admit instead." }
TACTIC EXTEND reflexivity DEPRECATED reflexivity_depr
[ "reflexivity" ] -> [ Tactics.intros_reflexivity ]
END
```
A warning is shown at the point where the tactic is used (either
a direct call or when defining another tactic):
Tactic `foo` is deprecated since XX. YY
YY is typically meant to be "Use bar instead.".
|
| |
| |
| |
| |
| | |
This is a function that keeps beeing asked or reimplemented. It doesn't hurt
adding it to the Ltac API.
|
|/
|
|
|
|
|
|
|
|
| |
We deprecate the corresponding functions in Pcoq.Gram. The motivation is
that the Gram module is used as an argument to Camlp5 functors, so that
it is not stable by extension. Enforcing that its type is literally the
one Camlp5 expects ensures robustness to extension statically.
Some really internal functions have been bluntly removed. It is unlikely
that they are used by external plugins.
|
| |
|
|\ |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
(Universes and Evd)
|
| | |
| | |
| | |
| | | |
Unused since fd7f056b155b2ebaafa3251a3c136117ebefc3e3.
|
| | | |
|
| | | |
|
| |/
|/| |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
It was forcing the macro to generate code that was useless.
|
| |/
|/| |
|
|\ \
| | |
| | |
| | | |
points of Camlp5
|
| |/
|/|
| |
| | |
Don't allow notations attached to uniform inductives
|
|\ \
| | |
| | |
| | | |
Z into three files
|
| | |
| | |
| | |
| | | |
Fixes #7857.
|
| | | |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
The parser is stupid and the syntax is almost the same as the previous one.
The only difference is that one needs to wrap OCaml code between { braces }
so that quoting works out of the box.
Files requiring such a syntax are handled specifically by the type system
and need to have a .mlg extension instead of a .ml4 one.
|
| | |
|
|\ \
| |/
|/| |
|
|\ \ |
|
|\ \ \
| | | |
| | | |
| | | | |
constants
|
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
Apparently it was not useful. I don't remember what I was thinking
when I added it.
|
|\ \ \ |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This brings more compatibility with handling of mutual primitive records
in the kernel.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a first step towards the acceptance of mutual record types in the
kernel.
|
| | | | | |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | | |
- we always rename
- we compile {clear}/view to /view{clear}
|
| | | | |
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | | |
We only use it locally, so we simply register the ML tactic inside the module
but we do not export the syntax.
|