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.)
33 lines
596 B
Text
33 lines
596 B
Text
notation:50 a "**" b:50 => b * a * b
|
|
notation "~" a => a+a
|
|
|
|
namespace Foo
|
|
notation "~~" a => a+a
|
|
end Foo
|
|
|
|
syntax:60 term "+++" term:59 : term
|
|
|
|
syntax "<||" term "||>" : term
|
|
|
|
macro_rules
|
|
| `($a +++ $b) => `($a + $b + $b)
|
|
|
|
macro_rules
|
|
| `(<|| $x ||>) => `($x +++ 1 ** 2)
|
|
|
|
|
|
/-- info: 2 * (2 + 1 + 1) * 2 : Nat -/
|
|
#guard_msgs in
|
|
#check <|| 2 ||>
|
|
|
|
/-- info: 2 * (2 + 2 + 1 + 1) * 2 : Nat -/
|
|
#guard_msgs in
|
|
#check <|| ~2 ||>
|
|
|
|
/-- info: 2 * (2 + 2 + 1 + 1) * 2 : Nat -/
|
|
#guard_msgs in
|
|
#check <|| ~~2 ||>
|
|
|
|
/-- info: 2 * (2 * (3 + 1 + 1) * 2 + 1 + 1) * 2 : Nat -/
|
|
#guard_msgs in
|
|
#check <|| <|| 3 ||> ||>
|