3a457e6ad6
Many of our tests in `tests/lean/run/` produce output from `#eval` (or `#check`) statements, that is then ignored. This PR tries to capture all the useful output using `#guard_msgs`. I've only done a cursory check that the output is still sane --- there is a chance that some "unchecked" tests have already accumulated regressions and this just cements them! In the other direction, I did identify two rotten tests: * a minor one in `setStructInstNotation.lean`, where a comment says `Set Nat`, but `#check` actually prints `?_`. Weird? * `CompilerProbe.lean` is generating empty output, apparently indicating that something is broken, but I don't know the signficance of this file. In any case, I'll ask about these elsewhere. (This started by noticing that a recent `grind` test file had an untested `trace_state`, and then got carried away.)
20 lines
566 B
Text
20 lines
566 B
Text
def Nat.hasDecEq: (a: Nat) → (b: Nat) → Decidable (Eq a b)
|
|
| 0, 0 => isTrue rfl
|
|
| n+1, 0
|
|
| 0, n+1 => isFalse Nat.noConfusion
|
|
| n+1, m+1 =>
|
|
match h:hasDecEq n m with -- it works without `h:`
|
|
| isTrue heq => isTrue (heq ▸ rfl)
|
|
| isFalse hne => isFalse (Nat.noConfusion · (λ heq => absurd heq hne))
|
|
termination_by a b => (a, b)
|
|
|
|
set_option pp.proofs true
|
|
|
|
/--
|
|
info: @[irreducible] def Nat.hasDecEq : (a b : Nat) → Decidable (a = b) :=
|
|
fun a b => Nat.hasDecEq._unary ⟨a, b⟩
|
|
-/
|
|
#guard_msgs in
|
|
#print Nat.hasDecEq
|
|
|
|
#print Nat.hasDecEq._unary
|