lean4-htt/tests/lean/run/coeIssues4.lean
Kim Morrison 3a457e6ad6
chore: use #guard_msgs in run tests (#4175)
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.)
2024-05-16 00:38:31 +00:00

38 lines
674 B
Text

--
def f : List Int → Bool := fun _ => true
def ex3 : IO Bool := do
let xs ← pure [1, 2, 3];
pure $ f xs -- Works
inductive Expr
| val : Nat → Expr
| app : Expr → Expr → Expr
instance : Coe Nat Expr := ⟨Expr.val⟩
instance : OfNat Expr n where
ofNat := Expr.val n
def foo : Expr → Expr := fun e => e
def ex1 : Bool :=
f [1, 2, 3] -- Works
def ex2 : Bool :=
let xs := [1, 2, 3];
f xs -- Works
def ex4 :=
[1, 2, 3].map $ fun x => x+1
def ex5 (xs : List String) :=
xs.foldl (fun r x => r.push x) Array.empty
set_option pp.all true in
/-- info: foo (@OfNat.ofNat.{0} Expr 1 (@instOfNatExpr 1)) : Expr -/
#guard_msgs in
#check foo 1
def ex6 :=
foo 1