Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Signature printing: fidelity roadmap

Open
#231 0 comments 0 reactions 0 assignees View on GitHub

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

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

enhancement

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from VirtusLab/cellar

All issues in VirtusLab/cellar

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.