leanprover / leanprover/lean4

invalid anchors when passing a typeclass to `grind`

Open
#13,764 0 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
Description

For a call directly using a typeclass, grind? will fail to report the class and also include invalid anchors.

Steps to Reproduce

An example:

example {α} {r : α → α → Prop} [Std.Refl r] (a : α) : r a a := by
  grind [Std.Refl]

where none of the grind? suggestions work for these reasons.

Expected behavior:

grind? includes the passed typeclass, and no invalid anchors.

Actual behavior:

Each grind? suggestion is either an empty grind only or has invalid anchors.

Versions

Lean 4.30.0-rc2
Target: x86_64-unknown-linux-gnu

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 reproducing the minimal Lean example with grind? on the specified nightly release, then compare the generated suggestions with the expected behavior. The issue is done when the passed typeclass is included and the suggestions contain no invalid anchors or empty grind only commands.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.