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.)
16 lines
492 B
Text
16 lines
492 B
Text
macro "mk_m " id:ident v:str n:num c:char : command =>
|
|
let tk := Lean.Syntax.mkStrLit id.getId.toString
|
|
`(macro $tk:str : term => `(fun (x : String) => x ++ $v ++ toString $n ++ toString $c))
|
|
|
|
#print " ---- "
|
|
|
|
mk_m foo "bla" 10 'a'
|
|
mk_m boo "hello" 3 'b'
|
|
|
|
/-- info: (fun x => x ++ "bla" ++ toString 10 ++ toString 'a') "world" : String -/
|
|
#guard_msgs in
|
|
#check foo "world"
|
|
|
|
/-- info: (fun x => x ++ "hello" ++ toString 3 ++ toString 'b') "boo" : String -/
|
|
#guard_msgs in
|
|
#check boo "boo"
|