Would probably be good to make `lvalue_p` operate on HIR nodes instead of trees
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 67
Description
Would probably be good to make `lvalue_p` operate on HIR nodes instead of trees
Originally posted by @powerboat9 in https://github.com/Rust-GCC/gccrs/issues/3300#issuecomment-2567128344
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 reading the linked discussion in issue #3300 and locating the lvalue_p entry point in the gccrs source. Trace whether it currently consumes trees or HIR nodes, then confirm the intended boundary and update scope with maintainers; done means lvalue_p operates on HIR nodes with relevant compiler tests still passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100