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.)
32 lines
558 B
Text
32 lines
558 B
Text
syntax (name := mycheck) "#check" sepBy(term, ",") : command
|
|
|
|
open Lean
|
|
|
|
macro_rules (kind := mycheck)
|
|
| `(#check $es,*) =>
|
|
let cmds := es.getElems.map $ fun e => mkNode `Lean.Parser.Command.check #[mkAtom "#check", e]
|
|
pure $ mkNullNode cmds
|
|
|
|
/-- info: Bool.true : Bool -/
|
|
#guard_msgs in
|
|
#check true
|
|
|
|
/--
|
|
info: Bool.true : Bool
|
|
---
|
|
info: Bool.true : Bool
|
|
-/
|
|
#guard_msgs in
|
|
#check true, true
|
|
|
|
/--
|
|
info: Bool.true : Bool
|
|
---
|
|
info: 1 : Nat
|
|
---
|
|
info: 3 : Nat
|
|
---
|
|
info: fun x => x + 1 : Nat → Nat
|
|
-/
|
|
#guard_msgs in
|
|
#check true, 1, 3, fun (x : Nat) => x + 1
|