Scoped traverser
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
A traverser that keeps track of scope (Lems->comp->subComp...) would make some of the logic more elegant and readable, replacing ugly constructs tied to the (auto generated) depth-first traverser.
- family visitor
- symbol visitor
- expression dim checker visitor
Contributor guide
No contributing guide indexed for this repository
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 locating the existing auto-generated depth-first traverser and the family, symbol, and expression dimension-checker visitors named in the issue. Read how those visitors currently track Lems-to-comp-to-subComp scope and identify the logic the proposed scoped traverser should replace. Done means the three visitors use the scoped traversal approach while preserving their existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100