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.)
18 lines
491 B
Text
18 lines
491 B
Text
import Lean
|
||
|
||
@[inline] private unsafe def mapMonoMImp [Monad m] (as : Array α) (f : α → m α) : m (Array α) :=
|
||
go 0 as
|
||
where
|
||
@[specialize] go (i : Nat) (as : Array α) : m (Array α) := do
|
||
if h : i < as.size then
|
||
let a := as[i]
|
||
let b ← f a
|
||
if ptrEq a b then
|
||
go (i+1) as
|
||
else
|
||
go (i+1) (as.set ⟨i, h⟩ b)
|
||
else
|
||
return as
|
||
|
||
set_option trace.Compiler.result true
|
||
run_meta Lean.Compiler.compile #[``mapMonoMImp, ``mapMonoMImp.go]
|