leanprover / leanprover/lean4

loop in typeclass inference at different depths

Open
#13,063 1 comment 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug P-high
Dominant language
Lean
Stars
9.2k
Forks
990
Avg merge
1d 17h
Merged PRs (30d)
175

Description

Prerequisites
Description

Loops are normally detected by typeclass inference. However, this is not the case if the loop happens at different depths, leading to max recursion or bad performance.

Context

This is a minimized version of a serious performance issue in Mathlib related to Riemannian geometry. Discussed at #mathlib4 > Slow Riemannian geometry @ 💬

Steps to Reproduce
class SGTop (α : Type)
class SGIsCont (α : Type) [SGTop α]
class SGNormed (α : Type) extends SGTop α

instance instIsContOfNormed {α : Type} [SGNormed α] : SGIsCont α where
instance instIsNormedOfBundle {α : Type} [SGTop α] [SGIsCont α] : SGNormed α where

variable {α : Type} [SGTop α]

set_option maxSynthPendingDepth 500

/--
error: failed to synthesize
  SGNormed α
maximum recursion depth has been reached
use `set_option maxRecDepth <num>` to increase limit
use `set_option diagnostics true` to get diagnostic information

Hint: Additional diagnostic information may be available using the `set_option diagnostics true` command.
-/
#guard_msgs in
#synth SGIsCont α

Expected behavior:

To synthetize SGIsCont α, Lean tries to apply instIsContOfNormed, and then instIsNormedOfBundle. For the latter to make sense, it needs SGIsCont α. Typeclass inference should see that there is a loop, and stop there.

Actual behavior:

Typeclass inference does not detect that there is a loop (probably because it's at depth one more), tries again the same instances, and this goes on forever, resulting in a maximum recursion error. With the standard values for maxSynthPendingDepth of 2 or 3, the loop stops after a few iterations, but this has still a very bad performance impact in Mathlib real-life situation.

Versions

Lean 4.29.0-rc6

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 minimized reproduction in the issue and the typeclass inference behavior controlled by maxSynthPendingDepth. Compare the nightly result with the expected loop detection at different depths. Done means the example terminates by recognizing the recursive SGIsCont/SGNormed cycle without reaching a maximum recursion 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
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.