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 | 8 |
1 files changed, 4 insertions, 4 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 7acb396f6..d7d670839 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 @@ -118,10 +118,10 @@ conversion, ultimately raising a Now we should look at how a library like Dask could benefit from ``like=``. Before we understand that, it's important to understand a bit about Dask basics -and ensures correctness with ``__array_function__``. Note that Dask can compute -different sorts of objects, like dataframes, bags and arrays, here we will focus -strictly on arrays, which are the objects we can use ``__array_function__`` -with. +and ensures correctness with ``__array_function__``. Note that Dask can perform +computations on different sorts of objects, like dataframes, bags and arrays, +here we will focus strictly on arrays, which are the objects we can use +``__array_function__`` with. Dask uses a graph computing model, meaning it breaks down a large problem in many smaller problems and merges their results to reach the final result. To |