diff options
Diffstat (limited to 'doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst')
| -rw-r--r-- | doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst b/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst index e09875d15..d0334967c 100644 --- a/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst +++ b/doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst @@ -162,7 +162,7 @@ To enable proper identification of the array type we use Dask's utility function function is primarily targeted at the library's internal usage to ensure chunks are created with correct types. Without the ``like=`` argument, it would be impossible to ensure ``my_pad`` creates a padding array with a type matching -that of the input array, which would cause cause a ``TypeError`` exception to +that of the input array, which would cause a ``TypeError`` exception to be raised by CuPy, as discussed above would happen to the CuPy case alone. Current NumPy users who don't use other arrays from downstream libraries should |