db491ddd35
This PR moves the issue tracking infrastructure from `GrindM` to `SymM`. Issues can occur in different places within a `sym =>` block (e.g., during arithmetic normalization, simplification), not just during `grind` invocations. Moving them to `SymM` makes them available to all modules operating within the symbolic computation framework. - `Sym.reportIssue`: adds an issue to the `SymM` state - `Sym.getIssues`: retrieves accumulated issues - `Sym.withNewIssueContext`: saves/restores the issue list around a computation, used at grind entry points to isolate per-invocation issues while preserving them in the outer context - `GrindM.State.issues` removed; `Grind.reportIssue` delegates to `Sym.reportIssue` 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
8 lines
210 B
Text
8 lines
210 B
Text
module
|
||
open Lean Grind
|
||
|
||
-- Should not produced spurious issues.
|
||
#guard_msgs (drop error, trace) in
|
||
set_option trace.sym.issues true in
|
||
example [Field α] (a b : α) : a*b + b*c = 2 → b = a⁻¹ := by
|
||
grind
|