| Age | Commit message (Collapse) | Author |
|
Reviewed-by: erikmd
Reviewed-by: silene
|
|
Reviewed-by: silene
|
|
time and use location in some typing error messages
Reviewed-by: ppedrot
|
|
Reviewed-by: Zimmi48
|
|
|
|
parameters in safe_env
Reviewed-by: herbelin
|
|
Reviewed-by: herbelin
Ack-by: gares
Ack-by: ejgallego
|
|
Reviewed-by: herbelin
Ack-by: SkySkimmer
|
|
Reviewed-by: Zimmi48
Reviewed-by: MSoegtropIMC
|
|
Reviewed-by: mattam82
Ack-by: Janno
Ack-by: gares
|
|
only-printing notations
Reviewed-by: SkySkimmer
|
|
|
|
We simply use evars instance in the right order while reading back VM values.
|
|
|
|
|
|
|
|
|
|
The (old) original model for notations was to associated both a
parsing and a printing rule to a notation.
Progressively, it become more and more common to have only parsing
notations or even multiple expressions printed with the same notation.
The new model is to attach to a given scope, string and entry at most
one either only-parsing or mixed-parsing-printing rules + an
arbitrarily many unrelated only-printing rules.
Additionally, we anticipate the ability to selectively
activate/deactivate each of those.
This allows to fix in particular #9682 but also to have
more-to-the-point warnings in case a notation overrides or partially
overrides another one.
Rules for importing are not changed (see forthcoming #12984 though).
We also improve the output of "Print Scopes" so that it adds when a
notation is only-parsing, only-printing, or deactivated, or a
combination of those.
Fixes #4738
Fixes #9682
Fixes part 2 of #12908
Fixes #13112
|
|
This is in anticipation of a model with an explicit difference between
a parsing-printing notation and the pair of only-parsing notation +
only-printing notation.
|
|
Also add optimisation of interpretation_eq.
|
|
This is to be consistent with the use of parentheses in the syntax of
Notation and to support a list of attribute afterwards.
|
|
deprecated.
|
|
|
|
missing.
|
|
Reviewed-by: SkySkimmer
|
|
Add menu item that uses this
|
|
Co-authored-by: Hugo Herbelin <herbelin@users.noreply.github.com>
|
|
Reviewed-by: SkySkimmer
Reviewed-by: ppedrot
Reviewed-by: ejgallego
|
|
|
|
The current implementation of par: is still in the STM, but is optional.
If the STM does not take over it, it defaults to the implementation of
in comTactic which is based on all: (i.e. sequential).
This commit also moved the interpretation of a tactic from g_ltac to
vernac/comTactic which is more appropriate.
Co-authored-by: Gaëtan Gilbert <gaetan.gilbert@skyskimmer.net>
|
|
Reviewed-by: ejgallego
Reviewed-by: silene
|
|
|
|
|
|
|
|
This fixes #12623 (bidirectionality breaks impredicativity).
|
|
Fix part of #8196, fix #12414
Replaces #9343
|
|
Reviewed-by: ppedrot
|
|
The safe environment features two different sets of delta resolvers, one for
module parameters and one for the actual body of the module being built. The
purpose of this separations seems to have been to reduce the number of name
equations being added to the environment, since the one from the parameters
would already be present at instanciation time.
Semantically, required modules behave like parameters in this respect, i.e.
delta resolvers that come from modules dependend upon are guaranteed to be added
when that module is actually required. As such, there is no need to store the
quotient coming from the dependencies inside the vo file of a given library.
Yet, the previous code would precisely do that, leading to a potential quadratic
blowup in vo file size, similarly to the issue with vio files storing the whole
chain of dependency. This patch fixes the issue simply by segregating those
redundant constraints in the dedicated field, thus dropping them from the vo.
|
|
|
|
|
|
An h-box inhibits the breaking semantics of any cut/spc/brk in the
enclosed box.
We tentatively replace its occurrence by an h or hv, assuming in
particular that if the indentation is not 0, an hv box was intended.
|
|
|
|
specific format.
Reviewed-by: ejgallego
|
|
Reviewed-by: SkySkimmer
|
|
|
|
Reviewed-by: ppedrot
|
|
Evarconv.apply_on_subterm
Reviewed-by: mattam82
|
|
Reviewed-by: ppedrot
|
|
Reviewed-by: ppedrot
|
|
I know higher-order mutable state shared across call sites is a staple of
Matthieu's style, but it is a footgun begging to be abused.
|