Split-up `ResolverBase` into multiple visitors
Open
Nobody has claimed this yet.
cleanup
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 20h 2m
- Merged PRs (30d)
- 66
Description
Eventually, we want to do the same refactoring @dkm did for HIR over here. Since it will clean it up alot.
Originally posted by @philberty in https://github.com/Rust-GCC/gccrs/pull/1172#discussion_r858802353
Reference HIR PR from @dkm: #954
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 locating ResolverBase and study the HIR refactoring referenced in PR #954, comparing it with the approach used in HIR. Define the visitor boundaries and confirm the intended split with maintainers; done means ResolverBase has been separated into multiple visitors with equivalent behavior and appropriate validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100