jackfirth / jackfirth/resyntax
Reader-only refactoring rules
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 70
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Some refactoring rules, especially those for small #lang-based DSLs like #lang resyntax/test, don't actually need the source code to be expanded and fully analyzed. There should be a way for refactoring rules to restrict themselves to "reader-only" behavior. If all rules in the refactoring suite for a source are reader-only, Resyntax should skip the expansion and analysis phases of its pipeline.
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 Resyntax's refactoring pipeline and how it handles rules for a source, including small #lang-based DSLs such as #lang resyntax/test. Determine how a suite can declare that all its rules are reader-only, then verify that expansion and analysis are skipped when appropriate.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100