leanprover / leanprover/lean4

Functional induction does not preserve match cases syntactically

Open
#5,282 1 comment 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

If I define a function on natural numbers using the equation compiler and have a case for n + 1, then the corresponding case in the functional induction principle is spelled n.succ.

Context

In #3629 we changed cases and induction such that they generate goals with n + 1 instead of n.succ. This is one case where functional induction is less nice to use than induction or the equation compiler.

Steps to Reproduce
def f : Nat → Nat
  | 0 => 0
  | n + 1 => f n

#check f.induct

Expected behavior: f.induct (motive : Nat → Prop) (case1 : motive 0) (case2 : ∀ (n : Nat), motive n → motive (n + 1)) : ∀ (a : Nat), motive a

Actual behavior: f.induct (motive : Nat → Prop) (case1 : motive 0) (case2 : ∀ (n : Nat), motive n → motive n.succ) : ∀ (a : Nat), motive a

Versions

4.12.0-nightly-2024-09-07 on live.lean-lang.org

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 minimal example with the equation compiler and #check f.induct, then trace how the functional induction principle is generated. The fix is done when the induction case for n + 1 is presented syntactically as motive (n + 1) rather than motive n.succ, with the example still type-checking.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.