Inconsistent type inference
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Prerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Checked that your issue isn't already filed.
- Reduced the issue to a self-contained, reproducible test case.
Description
This function:
def foo (a : Nat) (b) := a + b
resolves to foo : Nat → Nat → Nat
But this one does not:
def foo (a : Nat) (b) : Nat := a + b
saying failed to infer binder type when the resulting type of a declaration is explicitly provided, all holes (e.g., _) in the header are resolved before the declaration body is processed
Steps to Reproduce
See above.
Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
Lean (version 4.0.0-nightly-2022-09-12, commit ec2372e8d4ca, Release)
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run the two self-contained declarations from the issue with Lean 4 version 4.0.0-nightly-2022-09-12 and compare their inferred types and diagnostics. Trace the type-inference path for implicit binder types when an explicit result type is present; done means the second declaration accepts the binder and infers the same type as the first, with regression coverage for both examples.
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
- 42/100