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

Java benchmark: pair the members a record declares implicitly

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
54/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
java, scala
Domain
cli, tooling

Research direction

Start by reading JavaSourceDecls and JavaLanguage.isGenerated, then check how #222 prints records. The issue identifies implicit canonical constructors, component accessors, equals, hashCode and toString as the members to handle. Done when those record members are paired as generated and no longer reported as "Printed, not in source".

Written by the indexing model from the issue text.

Description

enhancement

A record's canonical constructor, component accessors, equals, hashCode and toString are in the classfile but not spelled out in the source, so the Java benchmark reports them as "Printed, not in source". io.micronaut:micronaut-core:5.2.16 (added to the defaults in #197) shows 35 of them across 5 records, which hides real extra members.

How: In JavaSourceDecls, emit the canonical constructor and one accessor per component from the record header unless the body declares them, and treat equals/hashCode/toString on records as generated in JavaLanguage.isGenerated. Depends on how #222 prints records.

🤖 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.