[release/10.0] fix Vector2/3 EqualsAny#124223
Merged
jeffhandley merged 8 commits intorelease/10.0from Feb 18, 2026
Merged
Conversation
Member
|
CC. @jeffhandley, @artl93 for initial bar check. |
artl93
approved these changes
Feb 12, 2026
Member
artl93
left a comment
artl93
left a comment
There was a problem hiding this comment.
New feature, customer reported, flaky behavior. Approved.
Member
|
/ba-g BadExit on unrelated test |
jeffhandley
approved these changes
Feb 16, 2026
jeffhandley
added
Servicing-approved
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
5 participants
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.
Backport of #123594 to release/10.0
/cc @tannergooding @kasperk81
Customer Impact
Reported in #123586, developers using some of the new APIs exposed on Vector2 and Vector3 could get non-deterministic results in some scenarios.
Regression
These are new APIs.
Testing
Explicit tests covering the scenarios were added in addition to manual verification of the codegen.
Risk
Low. These are net new APIs which could accidentally include invalid elements in the accelerated comparison. The fix was to ensure they used the existing centralized helpers that were exposed to help ensure such code was being consistently handled and avoid such problems. The APIs had simply not gotten checked in using them as intended.