From 17620c2ecb3dc6c2ab3164fa946c373a120d5619 Mon Sep 17 00:00:00 2001 From: Peter Andreas Entschev Date: Wed, 19 Aug 2020 18:44:09 +0200 Subject: Update doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst Co-authored-by: Eric Wieser --- doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/neps/nep-0035-array-creation-dispatch-with-array-function.rst') 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 9fb117005..c1edfa750 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 @@ -52,7 +52,7 @@ elsewhere and let NumPy handle them. But still these arrays have to be started in their native library and brought back. Instead if it was possible to create these objects through NumPy API then there would be an almost complete experience, all using NumPy syntax. For example, say we have some CuPy array -``cp_arr`` , and want a similar CuPy array with identity matrix. We could still +``cp_arr``, and want a similar CuPy array with identity matrix. We could still write the following: .. code:: python -- cgit v1.2.1