eclipse-xtext / eclipse-xtext/xtext
Collect outgoing siblings for UnorderedGroup
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
There is no distinction between ordered and unordered group when
creating the matcherstate. this causes elements in an unordered group
not to reach the end state when mixing optional and non-optional rules
because it is expected that they appear in-order.
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 tracing matcherstate creation and the handling of UnorderedGroup. Reproduce the case mixing optional and non-optional rules, then verify that unordered-group elements can reach the end state without being forced into order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100