Remove ExhaustiveOverride option
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.1k
- Forks
- 370
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 68
Description
Looking at #292 I realized I had forgotten about the ExhaustiveOverride option. I think we should remove it. It could give a performance gain in some cases, but it could also have a cost in safety since Java doesn't require @Override annotations by default. Overall I don't think it's worth keeping. @lazaroclapp thoughts?
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 issue #292 and searching the repository for the ExhaustiveOverride option. No files or tests are named; done means the option is removed consistently and the repository’s existing checks still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100