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.)
33 lines
1 KiB
Text
33 lines
1 KiB
Text
import Lean
|
||
|
||
/-- `erased α` is the same as `α`, except that the elements
|
||
of `erased α` are erased in the VM in the same way as types
|
||
and proofs. This can be used to track data without storing it
|
||
literally. -/
|
||
def Erased (α : Sort u) : Sort max 1 u :=
|
||
Σ's : α → Prop, ∃ a, (fun b => a = b) = s
|
||
|
||
namespace Erased
|
||
|
||
/-- Erase a value. -/
|
||
@[inline]
|
||
def mk {α} (a : α) : Erased α :=
|
||
⟨fun b => a = b, a, rfl⟩
|
||
|
||
open Lean.Compiler
|
||
set_option pp.explicit true
|
||
set_option pp.funBinderTypes true
|
||
set_option pp.letVarTypes true
|
||
set_option trace.Compiler.result true
|
||
/--
|
||
info: [Compiler.result] size: 1
|
||
def Erased.mk._redArg : PSigma lcErased lcErased :=
|
||
let _x.1 : PSigma lcErased lcErased := PSigma.mk lcErased ◾ ◾ ◾;
|
||
return _x.1
|
||
[Compiler.result] size: 1
|
||
def Erased.mk (α : lcErased) (a : lcErased) : PSigma lcErased lcErased :=
|
||
let _x.1 : PSigma lcErased lcErased := PSigma.mk lcErased ◾ ◾ ◾;
|
||
return _x.1
|
||
-/
|
||
#guard_msgs in
|
||
run_meta Lean.Compiler.compile #[``Erased.mk]
|