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.)
38 lines
846 B
Text
38 lines
846 B
Text
@[noinline] def f (x : Bool) := x
|
|
@[noinline] def g (x y : Bool) := x
|
|
|
|
def h (x : Bool) (xs : List Nat) : List Bool :=
|
|
match x with
|
|
| true =>
|
|
let z := f true
|
|
let y := f false
|
|
xs.map fun x => g y z
|
|
| false =>
|
|
let y := f false
|
|
let z := f true
|
|
xs.map fun x => g y z
|
|
|
|
theorem ex1 : h true [1] = h false [1] := rfl
|
|
|
|
#guard h true [1] == [false]
|
|
#guard h false [1] == [false]
|
|
|
|
theorem ex2 : (h true [1] == h false [1]) = true :=
|
|
by native_decide
|
|
|
|
@[noinline] def f2 (a : String) := a
|
|
@[noinline] def g2 (a : String) (x : Bool) := a
|
|
|
|
def h2 (x : Bool) (xs : List Nat) : List String :=
|
|
match x with
|
|
| false =>
|
|
let a := f2 "a"
|
|
let y := f false
|
|
xs.map fun x => g2 a y
|
|
| true =>
|
|
let y := f false
|
|
let a := f2 "a"
|
|
xs.map fun x => g2 a y
|
|
|
|
#guard h2 true [1] == ["a"]
|
|
#guard h2 false [1] == ["a"]
|