diff options
author | Hugo Herbelin <Hugo.Herbelin@inria.fr> | 2016-10-23 21:26:20 +0200 |
---|---|---|
committer | Hugo Herbelin <Hugo.Herbelin@inria.fr> | 2017-05-22 12:06:59 +0200 |
commit | 9eb2f7480de8ded94a1b96eb4f6cc16d19a8c14d (patch) | |
tree | 70115d49a0ca45c6fa06a5978878ccb7ae302987 /CHANGES | |
parent | 11851daee3a14f784cc2a30536a8f69be62c4f62 (diff) |
Clarifying the interpretation path for the "constr_with_binding" argument.
This fixes an inconsistency introduced in 554a6c806 (svn r12603) where
both interp_constr_with_bindings and interp_open_constr_with_bindings
were going through interp_open_constr (no type classes so as to not to
commit too early on irreversible choices, accepting unresolved holes).
We fix this by having interp_constr_with_bindings going to
interp_constr (using type classes and failing on unresolved evars).
The external impact is that any TACTIC EXTEND which refers to
constr_with_binding has now to decide whether it intends it to use
what the name suggest (using type classes and to fail if evars remain
unresolved), thus keeping constr_with_binding, or the actual behavior
which requires to use open_constr_with_bindings for strict
compatibility.
Diffstat (limited to 'CHANGES')
-rw-r--r-- | CHANGES | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -22,13 +22,16 @@ Tactics beta-iota-reduced after type-checking. This has an impact on the type of the variables that the tactic "refine" introduces in the context, producing types a priori closer to the expectations. +- In "Tactic Notation" or "TACTIC EXTEND", entry "constr_with_bindings" + now uses type classes and rejects terms with unresolved holes, like + entry "constr" does. To get the former behavior use + "open_constr_with_bindings" (possible source of incompatibility. Vernacular Commands - Goals context can be printed in a more compact way when "Set Printing Compact Contexts" is activated. - Standard Library - New file PropExtensionality.v to explicitly work in the axiomatic |