leanprover / leanprover/lean4

Using rcase/case tactic for recursive proofs when all arguments is variable cause an unexpected 'unknown identifier' error

Open
#8,282 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug P-low
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
namespace Working

variable {α : Type u} (as bs cs : List α)

theorem append_assoc (as : List α) : as ++ bs ++ cs = as ++ (bs ++ cs) := by
  rcases as with _ | ⟨a, as⟩
  . repeat rw [List.nil_append]
  . repeat rw [List.cons_append]
    apply congrArg
    rw [append_assoc]

end Working

namespace NotWorking

variable {α : Type u} (as bs cs : List α)

theorem append_assoc : as ++ bs ++ cs = as ++ (bs ++ cs) := by
  rcases as with _ | ⟨a, as⟩
  . repeat rw [List.nil_append]
  . repeat rw [List.cons_append]
    apply congrArg
    rw [append_assoc] -- Error: unknown identifier 'append_assoc'

end NotWorking

The code in NotWorking namespace is not working, it report an unknown identifier 'append_assoc' error.

But the code in Working namespace does working. The only difference is the as argument in Working namespace is an explicit argument, not from variable syntax.

Context

Zulip topic: #new members > unknown identifier if all args is defined in variable syntax

Steps to Reproduce
  1. Test the the code above locally or in online playground.

Expected behavior: Code in NotWorking also working as it has no semantic difference with Working one.

Actual behavior: The code in NotWorking namespace is not working, it report an unknown identifier 'append_assoc' error.

Versions

4.20.0-nightly-2025-05-10

Additional Information

N/A

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

Start by running the minimal Working and NotWorking examples in the issue against the reported nightly version. Investigate how recursive theorem names are resolved when arguments come from variable syntax versus explicit binders; done means both examples elaborate without the unknown identifier error.

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
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.