f650a1b873
I kept a few core methods (e.g., exact_core and apply_core). Reason:
if we use default parameters
meta constant exact (e : expr) (md := semireducible) : tactic unit
then, we will not be able to write
to_expr p >>= exact
The workaround is
do t <- to_expr p, exact t
or
to_expr p >>= (fun x, exact x)
One alternative is to change how we handle default parameters, and
eta-expand applications that involve default parameters.
We may also have an attribute [eta_expand]. Then
attribute [eta_expand] foo
instructs the elaborator to automatically eta-expand foo-applications.
The attribute would give users more control, and avoid potential
performance problems. Without the attribute, then for every function
application the elaborator has to check the type and decide whether it
must be eta-expanded or not.
@gebner @kha What do you think?
12 lines
317 B
Text
12 lines
317 B
Text
set_option pp.all true
|
||
open tactic
|
||
|
||
example : true := by do
|
||
a ← to_expr `((0 : ℕ)), b ← to_expr `(nat.zero),
|
||
fail_if_success (unify a b transparency.none),
|
||
triv
|
||
|
||
example (x : ℕ) : true := by do
|
||
a ← to_expr `((x + 0 : ℕ)), b ← to_expr `(x + nat.zero),
|
||
fail_if_success (unify a b transparency.none),
|
||
triv
|