leanprover / leanprover/lean4

apply results in hidden let values

Open
#9,994 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug P-medium
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:

Description

The post state of the apply tactic results in the value of local declarations being hidden. From my reading of the pp code at https://github.com/leanprover/lean4/blob/48365b6052da47426e440f21b7703d5f7646c7c8/src/Lean/Meta/PPGoal.lean#L91 it seems this happens when a non-synthetic opaque metavariable is created, but I don't see exactly where here.

example : False := by
  let a := 1
  trace_state
  /- 
  a : Nat := 1
  ⊢ False -/
  apply id
  trace_state
  /-case a
  a : Nat := ⋯
  ⊢ False -/

I expect both to produce the same state.

Versions

live latest 4.23-rc1

Impact

Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the example in the issue against the Lean nightly release and compare the two trace_state outputs before and after apply id. Start with the referenced src/Lean/Meta/PPGoal.lean code and trace how hidden local values are selected; done means the post-apply state preserves the visible value of a as in the initial state.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.