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.)
31 lines
530 B
Text
31 lines
530 B
Text
import Lean
|
|
|
|
open Lean
|
|
|
|
/-- info: Lean.mkNullNode (args : Array Syntax := #[]) : Syntax -/
|
|
#guard_msgs in
|
|
#check mkNullNode
|
|
|
|
/-- info: mkNullNode #[] : Syntax -/
|
|
#guard_msgs in
|
|
#check mkNullNode #[]
|
|
|
|
/-- info: @mkNullNode : optParam (Array Syntax) #[] → Syntax -/
|
|
#guard_msgs in
|
|
#check @mkNullNode
|
|
|
|
/--
|
|
info: let f := @mkNullNode;
|
|
f #[] : Syntax
|
|
-/
|
|
#guard_msgs in
|
|
#check
|
|
let f : Array Syntax → Syntax := @mkNullNode;
|
|
f #[]
|
|
|
|
/--
|
|
info: let f := @mkNullNode;
|
|
f #[] : Syntax
|
|
-/
|
|
#guard_msgs in
|
|
#check let f := @mkNullNode; f #[]
|