`set_option in` makes local attribute ineffective
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Prerequisites
Please put an X between the brackets as you perform the following steps:
- Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues - Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries. - Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
Description
The construction
set_option ... in
attribute [local ...] ...
silently fails to add the attribute. I believe this is because the set_option in is desugared into a section and the attribute becomes local to that section, which is then immediately closed again.
Steps to Reproduce
MWE:
axiom falso : False
section Works
attribute [local simp] falso
example : False := by simp
end Works
section Fails
set_option trace.debug true in
attribute [local simp] falso
example : False := by simp -- simp made no progress
end Fails
Versions
"4.11.0-nightly-2024-07-12"
Impact
Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the minimal reproducer in the issue and inspect how set_option ... in handles the following local attribute declaration, especially its interaction with section scope. Done means the attribute [local simp] falso remains effective for the subsequent example while option scoping still works.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100