Skip to content

Allow any combination of real dtypes in comparisons #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 10, 2024

Conversation

asmeurer
Copy link
Member

This does not change == or != because the standard is currently unclear about that so I'd like to see what happens there first.

asmeurer added 3 commits July 10, 2024 13:01
This does not change == or != because the standard is currently unclear about
that so I'd like to see what happens there first.
Also update elementwise function tests to check for disallowed type
promotions, not just disallowed mixed kind types.
@asmeurer
Copy link
Member Author

Actually I went ahead and updated equal/not_equal/==/!= because it was easier.

@asmeurer
Copy link
Member Author

The test suite needs to be updated to test for this (and that will need to wait for update to the spec). I need this to unblock the CI here for #49 which is also blocking the test suite CI.

@asmeurer asmeurer enabled auto-merge July 10, 2024 19:36
@asmeurer asmeurer merged commit 77a9c2d into data-apis:main Jul 10, 2024
21 checks passed
@asmeurer
Copy link
Member Author

It's looking like the standard is going to be updated to match the existing behavior, so this should be reverted data-apis/array-api#822.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant