typelevel / typelevel/frameless
Benchmark compilation time
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Scala
- Stars
- 895
- Forks
- 135
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 3
Description
Would be nice to use shapeless.test.compileTime or something to check that we don't accidentally introduce regression in compilation time.
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 reading the linked shapeless.test.compileTime implementation and then inspect Frameless's existing test and build setup for a suitable compilation check entry point. The work is done when a repeatable check detects unintended compilation-time regressions without disrupting the existing test workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100