-
Notifications
You must be signed in to change notification settings - Fork 45
Issues with test_clip #276
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
Comments
The first thing is kind of a flaw in the standard decision to make The second is an annoying corner case in the standard, where apparently you can't compare uint64 and int64 (or at least the strict library doesn't allow it). I wonder if there's a helper function already somewhere in the test suite that makes this easier. |
Actually for the comparison, we should avoid using Python integers that are larger than the bounds of x.dtype as the input. We should also probably avoid allowing int64 and uint64, even though there technically isn't a promotion, since libraries won't be able to do the proper comparisons we need for the test (it looks like the standard might be changed to not require this data-apis/array-api#819). |
The issues with test_clip should be mostly ironed out now. |
The text was updated successfully, but these errors were encountered: