Sebastian Ullrich 8d3be96024 fix: tactics in terms in tactics may break incremental reporting (#4436) ... A pending tactic mvar managed to escape into an unexpected context in specific circumstances. ```lean example : True := by · rw [show 0 = 0 by rfl] ``` * Term elaboration of the `show` creates a pending mvar for the `by rfl` proof * `rw` fails with an exception because the pattern does not occur in the target * `cdot` catches the exception and admits the goal * `Term.runTactic` [synthesizes all pending mvars from the tactic's execution](5f9dedfe5e/src/Lean/Elab/SyntheticMVars.lean (L350)), including the `by rfl` proof. But this would not have happened without `cdot` as the exception would have skipped that invocation! * Now incrementality is confused because the nested `by rfl` proof is unexpectedly run in the same context as the top-level proof, writing to the wrong promise, and the error message is lost Solution: disable incrementality for these pending mvars		2024-06-12 14:59:24 +00:00
..
bench	chore: Nat.repr microbenchmark (#3888)	2024-04-17 18:10:32 +00:00
compiler
elabissues
ir
lean	fix: tactics in terms in tactics may break incremental reporting (#4436)	2024-06-12 14:59:24 +00:00
pkg	feat: incremental elaboration of definition headers, bodies, and tactics (#3940)	2024-05-22 13:23:30 +00:00
playground
plugin
simpperf
.gitignore
common.sh
lean-toolchain