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.)
28 lines
516 B
Text
28 lines
516 B
Text
import Lean
|
|
|
|
|
|
namespace Foo
|
|
open Lean.Elab.Term
|
|
|
|
syntax (name := fooKind) "foo!" term : term
|
|
|
|
@[term_elab fooKind] def elabFoo : TermElab :=
|
|
fun stx expectedType? => elabTerm (stx.getArg 1) expectedType?
|
|
|
|
/-- info: 10 : Nat -/
|
|
#guard_msgs in
|
|
#check foo! 10
|
|
|
|
end Foo
|
|
|
|
namespace Lean
|
|
namespace Elab
|
|
namespace Tactic
|
|
open Meta
|
|
|
|
@[builtin_tactic clear] def myEvalClear : Tactic := -- this fails in the old-frontend because it eagerly resolves `clear` as `Lean.Meta.clear`.
|
|
fun _ => pure ()
|
|
|
|
end Tactic
|
|
end Elab
|
|
end Lean
|