Signature printing: fidelity roadmap
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- scala
- Domain
- cli, developer-experience
Research direction
Read the benchmark and printer roadmap items linked from this tracker, starting with #197 for benchmark infrastructure. This issue groups work that must be handled in separate issues and includes no specific file or change to make; completion is when the listed items are implemented and their PRs merge.
Written by the indexing model from the issue text.
Description
Tracks the work to make cellar's printed signatures match what libraries declare, verified by the signature benchmark. Each item has its own issue; check it off when its PR merges.
Done
- Java symbols in Java syntax and the Java signature benchmark (#192)
Benchmark infrastructure
- Scala 2/3 benchmark,
compare.sh, and a diff report on every PR (#197) - Newer Java in the benchmark (#190)
Scala fixes implemented on the backup branch
Implemented on backup/scala-signature-bench; each becomes its own PR from main after #197 merges, with the review findings listed in its issue.
- #201
- #202
- #203
- #204
- #205
- #206
- #207
- #208
- #209
Printer improvements
Roughly in priority order of value to an agent: anonymous givens, extension methods, deprecation first.
- #210
- #211
- #212
- #213
- #214
- #215
- #216
- #217
- #218
- #219
- #220
- #221
- #222
- #250
- #257
Listings
- #223
- #224
- #225
- #226
Signature benchmark
- #227
- #228
- #229
- #230
- #236
🤖 Generated with Claude Code
- Dominant language
- Scala
- Stars
- 100
- Forks
- 12
- Avg merge
- 16h 11m
- Merged PRs (30d)
- 40
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from VirtusLab/cellar
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 1-2 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
All issues in VirtusLab/cellar
Similar issues
-
requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/datafusion-comet#7176 ·
Maintainers usually reply within 1 day
-
kind:bug state:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenLineage/OpenLineage#5100 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
http4s/http4s#8015 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
testcontainers/testcontainers-scala#623 ·
Maintainers usually reply within 1 day
-
? - Needs Triage bug shuffle
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NVIDIA/cudf-spark#16528 ·
Maintainers usually reply within 1 day