lean4-htt/tests/lean/run/6655.lean
Joachim Breitner 117f73fc84
feat: linter.unusedSimpArgs (#8901)
This PR adds a linter (`linter.unusedSimpArgs`) that complains when a
simp argument (`simp [foo]`) is unused. It should do the right thing if
the `simp` invocation is run multiple times, e.g. inside `all_goals`. It
does not trigger when the `simp` call is inside a macro. The linter
message contains a clickable hint to remove the simp argument.

I chose to display a separate warning for each unused argument. This
means that the user has to click multiple times to remove all of them
(and wait for re-elaboration in between). But this just means multiple
endorphine kicks, and the main benefit over a single warning that would
have to span the whole argument list is that already the squigglies tell
the users about unused arguments.

This closes #4483.

Making Init and Std clean wrt to this linter revealed close to 1000
unused simp args, a pleasant experience for anyone enjoying tidying
things: #8905
2025-06-22 09:10:21 +00:00

111 lines
2.4 KiB
Text
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

/-!
# Improve zeta-delta tracking for `simp?`
https://github.com/leanprover/lean4/issues/6655 reports issues with `simp?` where
it would over-report local variables. This comes down to two kinds of issues:
- zeta-delta tracking wasn't being reset, so previous `simp?`s would contribute variables
- `simp?` would report variables that weren't explicitly mentioned,
because `whnf` would be run with different configurations during the tracking.
(e.g. `withInferTypeConfig` enables `zetaDelta`.)
This file tests that it resets the tracking and filters the list.
-/
set_option linter.unusedSimpArgs false
/-!
Example from #6655. This used to suggest `simp only [e, d]`.
-/
/--
info: Try this: simp only [e]
---
trace: α : Type
c : αα
x : α
d : αα := c
e : αα := d
⊢ d x = x
---
warning: declaration uses 'sorry'
-/
#guard_msgs in
example {α : Type} (c : αα) (x : α) : c x = x := by
let d := c
let e := d
change e x = x
simp? [e]
trace_state
sorry
/-!
Example from #6655. This used to suggest `simp only [d]`.
-/
/--
info: Try this: simp only
---
warning: declaration uses 'sorry'
-/
#guard_msgs in
example {α : Type} (c : αα) (x : α) : c x = x := by
let d := c
change d x = x
simp [d]
have : x = x := by
simp?
sorry
/-!
Example from comments of #6655. This used to suggest `simp only [Int.add_sub_cancel, p]`.
(N.B. the goal at that point does not have `p` in it!)
-/
/-- info: Try this: simp only [Int.add_sub_cancel] -/
#guard_msgs in
example (a b : Int) : a + b - b = a := by
let p := 1
have h : p = 1 := by
simp only [p]
simp?
/-!
Example from https://github.com/leanprover/lean4/pull/7539 by JovanGerb.
This used to suggest `simp only [a, b] ` and `simp only [a, b]`
-/
/--
info: Try this: simp only [a]
---
info: Try this: simp only
-/
#guard_msgs in
example : True := by
let a := 1
let b := 2
have : b = 2 := by simp [a,b]
have : a = 1 := by simp? [a]
have : 1 = 1 := by simp?
trivial
/-!
Test that there is still a deficiency. This should say `simp only [e]`.
-/
/--
info: Try this: simp only [e, c]
---
trace: α : Type
b : αα
x : α
c : αα := b
d : αα := c
e : αα := d
⊢ d x = x
---
warning: declaration uses 'sorry'
-/
#guard_msgs in
example {α : Type} (b : αα) (x : α) : b x = x := by
let c := b
let d := c
let e := d
change e x = x
simp? [e, c]
trace_state
sorry