fine-grained control of check syntax library
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
It would be better to have the ability to control which functions are executed and which are not in the drracket/check-syntax library.
The motivation is that certain functions, such as the function that powers add-docs-menu, are super slow, take several seconds to run on hundreds lines of code. But some other functions are be 10x faster. If an IDE plugin needs to run only a subset of the functions, it can obtain a lot of speed improvements.
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
Read the drracket/check-syntax library and trace the function that powers add-docs-menu to understand how check-syntax functions are selected and executed. Define a way for an IDE plugin to run only a subset, then verify that selected functions run while omitted functions do not and that the slow path can be avoided.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100