Repository navigation
Preserve exact integer differences in claim distances - #4
Merged
Merged
Conversation
ctoth
marked this pull request as ready for review
October 19, 2026 23:17
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.
Adjacent signed-64-bit integers above binary64's consecutive-integer range were assigned zero distance because both endpoints were rounded before subtraction. Subtract integer pairs exactly before converting the distance to the existing float result, preserving the unique SIGMA winner for a two-to-one profile.
Added regressions at positive and negative integer boundaries and for exact SIGMA scores. The new test file failed all six cases before the fix and passed all six afterward.
Closes #3