Keep goal view active on unparsed input
Open
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
example : True := by
skip
ski
example : True := by
skip
exact \<
ski and \< are parse errors and thus not part of the info tree ranges. We should make sure they are considered trailing input to the skip node and thus share its goal view.
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 with the two Lean examples in the issue and inspect how parse errors are excluded from info tree ranges and how trailing input is associated with the skip node. Verify the goal view for ski and \< after the change, including that both inputs share the skip goal view.
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
- 45/100