perf(core): avoid primitive fingerprint boxing#61
Merged
Conversation
Arbousier1
force-pushed
the
codex/perf-delimited-primitives
branch
from
July 16, 2026 05:53
7981752 to
4d6f998
Compare
Member
Author
|
Trusted base-owned performance A/B evidence:
|
TypeThe0ry
marked this pull request as ready for review
July 16, 2026 06:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
boolean,char, andintoverloads toDelimitedFingerprintBuilder.fieldWhy
Hot render/HUD signature paths currently route primitive values through
field(Object), which boxes them and materializes an intermediate string before appending. The primitive overloads append directly to the existingStringBuilder. Thecharoverload is required so Java widening tointcannot change character output.Validation
No Gradle, JMH, test, or server workload was run locally, per project policy. GitHub Build/Test is the functional gate. This PR stays draft and must not merge until the base-owned A/B lock fix (#60) lands and the protected fingerprint profile reports
PASS_OPTIMIZED; a separate base-owned harness change will also enforce exact JMH output and allocation evidence.