You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ndgrigorian Following up here, it is not guaranteed that the Array API standard will require device kwarg support, as there are some concerns as to whether such support is desirable. If you have particular thoughts on whether it should be required, please provide that input on the PR and/or associated issue. Thanks!
It has been decided against implementing device keyword in these functions. When all arguments are dtype, full type promotion graph is to be used. When some arguments are arrays, devices must be the same, and the device-specific type promotion graph is to be used.
Hence, the recommended usage is xp.can_cast( array, to_dtype) rather than xp.can_cast(array.dtype, to_dtype).
We still should adjust implementation of dpctl.tensor.can_cast and dpctl.tensor.result_type to conform to this specification.
The array API standard will soon require the
device
keyword be added tocan_cast
andresult_type
See:
data-apis/array-api#691
The text was updated successfully, but these errors were encountered: