perf: single pass
Open
- Dominant language
- JavaScript
- Stars
- 5.1k
- Forks
- 187
- PR merge metrics
- No merged PRs in 30d
Description
Right now write-good scans the input many times to find mistakes.
I think some of these can be consolidated into a single pass
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how write-good scans its input and cataloguing the separate passes used to find mistakes. Determine which passes can safely be consolidated without changing lint results; done means a justified single-pass design with equivalent behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100