Repository navigation
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.
Adds array/array coverage for the reflected elementwise operators in #301. Compares
a.__op__(b)andb.__rop__(a)for dtype, broadcast shape, and values, including 0-D arrays, while retaining the scalar cases.Validated with array-api-strict 2.6.1 and NumPy 2.4.6: 60 new cases passed per backend, plus 170 related tests with 5 existing remainder skips. Meta-tests: 70 passed, 1 existing skip; flake8 passes. An isolated subtraction-order mutation passes the old scalar/forward checks and fails the new test.