diff options
author | Hugo Herbelin <Hugo.Herbelin@inria.fr> | 2015-12-21 22:19:34 +0100 |
---|---|---|
committer | Hugo Herbelin <Hugo.Herbelin@inria.fr> | 2016-06-18 13:09:16 +0200 |
commit | f841c27c1cfd38aada72f3c8f90e2ed1ec22db6a (patch) | |
tree | 1595db648f65e4f381034a2385f4faa3b88f60cb /test-suite/success/specialize.v | |
parent | 1744e371d8fa2a612e3906c643fb5558a54a484f (diff) |
Adding an "as" clause to specialize.
Comments
--------
- The tactic specialize conveys a somehow intuitive reasoning concept
and I would support continuing maintaining it even if the design
comes in my opinion with some oddities. (Note that the experience of
MathComp and SSReflect also suggests that specialize is an
interesting concept in itself).
There are two variants to specialize:
- specialize (H args) with H an hypothesis looks natural: we
specialize H with extra arguments and the "as pattern" clause comes
naturally as an extension of it, destructuring the result using the
pattern.
- specialize term with bindings makes the choice of fully applying the
term filling missing expressions with bindings and to then behave as
generalize. Wouldn't we like a more fine-grained approach and the
result to remain in the context?
In this second case, the "as" clause works as if the term were posed
in the context with "pose proof".
Diffstat (limited to 'test-suite/success/specialize.v')
-rw-r--r-- | test-suite/success/specialize.v | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/test-suite/success/specialize.v b/test-suite/success/specialize.v index 3faa1ca43..fba05cd90 100644 --- a/test-suite/success/specialize.v +++ b/test-suite/success/specialize.v @@ -64,3 +64,11 @@ assert (H:=H I). match goal with H:_ |- _ => clear H end. match goal with H:_ |- _ => exact H end. Qed. + +(* Test specialize as *) + +Goal (forall x, x=0) -> 1=0. +intros. +specialize (H 1) as ->. +reflexivity. +Qed. |