leanprover / leanprover/lean4

`.brecOn` theorem is not marked as aux recursor

Open
#7,832 0 comments 1 reaction 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

On Prop-valued inductives, .brecOn is not marked as an aux recursor according to Lean.isAuxRecursor.

Context

I noticed this while trying to filter out definitions which are aux recursors.

Steps to Reproduce
import Lean

inductive Ex1 : Prop where
  | next : Ex1 → Ex1

inductive Ex2 : Type where
  | next : Ex2 → Ex2

-- compare with `.casesOn`
/--
info: true
-/
#guard_msgs in
run_meta do IO.println <| Lean.isAuxRecursor (← Lean.getEnv) ``Ex1.casesOn
/--
info: true
-/
#guard_msgs in
run_meta do IO.println <| Lean.isAuxRecursor (← Lean.getEnv) ``Ex2.casesOn


/--
info: false
-/
#guard_msgs in
run_meta do IO.println <| Lean.isAuxRecursor (← Lean.getEnv) ``Ex1.brecOn
/--
info: true
-/
#guard_msgs in
run_meta do IO.println <| Lean.isAuxRecursor (← Lean.getEnv) ``Ex2.brecOn

-- this could be consistent, and is not a limitation of how aux recursors work
run_cmd Lean.modifyEnv fun env => Lean.markAuxRecursor env ``Ex1.brecOn

/--
info: true
-/
#guard_msgs in
run_meta do IO.println <| Lean.isAuxRecursor (← Lean.getEnv) ``Ex1.brecOn

Expected behavior: All the run_metas output true

Actual behavior: there is inconsistency

Versions
  • Lean 4.19.0-rc2
    Target: x86_64-unknown-linux-gnu
  • Lean 4.18.0-rc1
    Target: x86_64-w64-windows-gnu Windows
  • Lean 4.20.0-nightly-2025-04-05
    Target: x86_64-unknown-linux-gnu
  • Lean 4.18.0
    Target: x86_64-unknown-linux-gnu
Additional Information

This could be related to the fact that Ex1.brecOn is a theorem but Ex2.brecOn is a def.

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 with the minimal reproduction using Lean.isAuxRecursor, Ex1.brecOn, Ex2.brecOn, and Lean.markAuxRecursor. Compare how the aux-recursor marking differs for Prop- and Type-valued inductives, including the theorem-versus-def distinction noted in the issue. Done means the supplied checks consistently report true without manual marking.

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.