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".

1 files changed, 1 insertions, 1 deletions

diff --git a/tactics/tactics.mli b/tactics/tactics.mli
index 012c75091a..fb033363e8 100644
--- a/tactics/tactics.mli
+++ b/tactics/tactics.mli
@@ -174,7 +174,7 @@ val unfold_body   : Id.t -> unit Proofview.tactic
 val keep          : Id.t list -> unit Proofview.tactic
 val apply_clear_request : clear_flag -> bool -> constr -> unit Proofview.tactic
 
-val specialize    : constr with_bindings -> unit Proofview.tactic
+val specialize    : constr with_bindings -> intro_pattern option -> unit Proofview.tactic
 
 val move_hyp      : Id.t -> Id.t move_location -> unit Proofview.tactic
 val rename_hyp    : (Id.t * Id.t) list -> unit Proofview.tactic