leanprover / leanprover/lean4

Resolving meta variables in function applications through TC synthesis

Open
#10,875 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

Consider:

class A (a : Nat) (b : Nat) (c : outParam Nat) where 
  wit : Nat × Nat × Nat := ⟨ a , b , c ⟩
instance instAZero : A (.zero) (n) (n) where 
instance instASucc [A m n o]  : A (.succ m) (n) (.succ o) where

#eval A.wit 1 2
#eval @A.wit 1 2 _

Lean is able to execute the first version perfectly fine and in particular automatically resolves the c argument through TC synthesis assigning it with the outParam mechanism. However when passing an _ explicitly this mechanism does not kick in.

Context

Brought up to me by @MangoIV

Expected behavior: Both versions should type check and execute the same way

Actual behavior: Only the first version type checks, the second fails to resolve the mvar

Versions

Lean 4.25.0-nightly-2025-10-21
Target: x86_64-unknown-linux-gnu

Additional Information

[Additional information, configuration or data that might be necessary to reproduce the issue]

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 Lean example in the issue and reproduce it against the specified nightly release, comparing implicit and explicit _ applications of A.wit. Investigate typeclass synthesis and outParam handling; done means both versions type check and execute equivalently without Mathlib or Batteries.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.