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

Scala: print `override` on overriding members

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
67/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
scala
Domain
cli

Research direction

Find where member modifiers such as implicit and final are printed from symbol flags, and update the Scala signature benchmark's source side so it retains override. Start by locating those printer and benchmark entry points, then run the relevant signature benchmark. Done when overriding members print override and the benchmark reports no modifiers regression.

Written by the indexing model from the issue text.

Description

enhancement

A member that overrides a parent's prints like any other, though its declaration says override and TASTy keeps the Override flag (dotty prints it). For an agent, override says that the member's contract and Scaladoc live on the parent, and, together with abstract, which members of a hierarchy are already implemented.

- def toString: String
+ override def toString: String

How: Print override from the symbol's flags, as implicit and final are. The Scala signature benchmark's source side drops override today, so it needs to keep it in the same PR, or every overriding member reports a "modifiers" regression.

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