leanprover-community / leanprover-community/lean
segfault on inductive type with binder starting with `_`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 434
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
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.
- Specifically, check out the wishlist, open RFCs,
or feature requests.
- Specifically, check out the wishlist, open RFCs,
- Reduced the issue to a self-contained, reproducible test case.
- Checked that your issue isn't already filed.
Description
If you create an inductive type with one constructor containing a field starting with an underscore, and then later use . notation, Lean will segfault.
Steps to Reproduce
inductive S
| mk : Π (_foo : nat → int), S
namespace S
def bar (s : S) : nat := 0
variable s : S
#check s.bar
end S
Expected behavior: s.bar : ℕ
Actual behavior: Lean segfaults
Reproduces how often: 100%
Essential features:
- the field
_foohas a name starting with an underscore - the inductive type has exactly one constructor
- the type of
_foois a Pi-type
Lean thinks that S is a structure and _foo is a field containing a parent structure ("subobject") foo.
Versions
Lean (version 3.18.4, commit f539be1e867c, Release)
linux
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 self-contained Lean reproducer from the issue and confirm that #check s.bar segfaults. Trace the handling of inductive types with a single constructor, underscore-prefixed fields, Pi-types, and dot notation; done means the check reports s.bar : ℕ without crashing.
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
- Mostly clear
- Newbie friendliness
- 38/100