Lean can't understand field notation inside a lambda inside a match arm
Nobody has claimed this yet.
- 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:
- Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues - Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries. - Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
Description
This code fails to type check:
#check match () with | _ => [0].map (·.toInt8)
Context
None.
Steps to Reproduce
See this code at https://live.lean-lang.org/#project=lean-nightly&codez=MQYwFgpiDWAEC2BDALuWAKAlLA7gS2TFgB9YB9WAXgD5YBtABgF0A6JABwwHaXkB7AJIA7ZAA5MQA
Expected behavior: This code passes type check.
Actual behavior:
invalid field notation, type is not of the form (C ...) where C is a constant
x✝
has type
?m.79
Versions
4.16.0-nightly-2024-12-12
Additional Information
None.
Impact
Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.
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
Start by reproducing the minimal snippet #check match () with | _ => [0].map (·.toInt8) on the Lean nightly release using the linked Live Lean test case. Investigate field-notation elaboration when the lambda appears inside a match arm. Done means the snippet passes type checking without the reported invalid-field-notation 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
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100