jackfirth / jackfirth/resyntax
UTS checker and renderer are completely untested
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 70
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
No test constructs UTS-annotated syntax, so check-universal-tagged-syntax and check-source-universal-tagged-syntax in private/universal-tagged-syntax.rkt (60.5% coverage) and syntax-replacement-render-using-uts in private/syntax-replacement.rkt never run — about 95 uncovered lines combined. Testing them means hand-building syntax objects with uts-content and uts-separators properties.
This might be worth deferring until #586 settles the UTS spec rather than pinning tests to a moving prototype, but filing it so the gap is tracked.
Part of #680.
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
Read private/universal-tagged-syntax.rkt and private/syntax-replacement.rkt, focusing on check-universal-tagged-syntax, check-source-universal-tagged-syntax, and syntax-replacement-render-using-uts. Review the UTS decisions in #586 before writing tests that construct syntax objects with uts-content and uts-separators. Done means the uncovered paths are exercised without pinning tests to behavior the prototype may change.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100