Repository navigation
fix(distance): keep antipodal distances finite - #3185
Open
Doomguy-BFG9000 wants to merge 1 commit into
Open
Doomguy-BFG9000 wants to merge 1 commit into
Doomguy-BFG9000 wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Fixes #3182.
Cap the haversine intermediate at 1 before taking its square-root complement. Floating-point rounding can otherwise make the complement negative for antipodal points, producing
NaNindistanceand calculations that depend on it.The new tests cover an antipodal pair and a nearby pair whose shorter arc is below half a circumference. On Windows with Node.js 24, the build, workspace tests, and targeted ESLint and Prettier checks passed. The root
pnpm teststopped in Monorepolint with the same Windows file-URL error reproduced on the base source.