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.)
20 lines
553 B
Text
20 lines
553 B
Text
|
|
|
|
axiom TrustMe {p : Prop} : p
|
|
|
|
def x := (1, 2)
|
|
def y := x
|
|
@[noinline] def mk (v : Nat) := (v, v+1)
|
|
|
|
#eval withPtrAddr x (fun a => dbgTrace (">> " ++ toString a) $ fun _ => 0) TrustMe
|
|
|
|
/-- info: true -/
|
|
#guard_msgs in
|
|
#eval withPtrEq x y (fun _ => dbgTrace (">> " ++ toString x ++ " == " ++ toString y) $ fun _ => x == y) TrustMe -- should not print message
|
|
|
|
/--
|
|
info: >> (1, 2) == (1, 2)
|
|
true
|
|
-/
|
|
#guard_msgs in
|
|
#eval withPtrEq x (mk 1) (fun _ => dbgTrace (">> " ++ toString x ++ " == " ++ toString y) $ fun _ => x == y) TrustMe -- should print message
|