PaperMC / PaperMC/codebook

Enum ordinals

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

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
22
Forks
1
Avg merge
2m
Merged PRs (30d)
1

Description

The integer returned by Enum#ordinal should not just use the i# format, but should be something associated with the type of the enum, like for Direction, it could be directionOrdinal.

All in the name of reducing the number of primitive local variables that have numbers after them.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue names no files, tests, or entry points. Start by locating the Enum#ordinal handling in the jar remapping logic and trace how local variable names are generated. Done means enum ordinal variables use names associated with their enum type, such as directionOrdinal for Direction, without introducing conflicting names.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.