Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,10 +161,13 @@ issue, but this hasn't necessarily been tested thoroughly.

3. Since NumPy is a CPU-only library, the [device
support](https://data-apis.org/array-api/latest/design_topics/device_support.html)
in array-api-strict is superficial only. `x.device` is always a (private)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't work out how the returned device object was private, so removed this part, but please correct if this is wrong.

`CPU_DEVICE` object, and `device` keywords to creation functions only
accept either this object or `None`. A future version of array-api-strict
[may add support for a CuPy
in array-api-strict is superficial only.
array-api-strict supports three 'devices'; the default `CPU_DEVICE`,
`Device("device1")` and `Device("device2")`. This allows testing of arrays on
different devices, without the need for special hardware.
`x.device` is always a `Device` object, and `device` keywords to creation
functions only accept the above three device objects or `None`. A future version of
array-api-strict [may add support for a CuPy
backend](https://github.com/data-apis/array-api-strict/issues/5) so that
more significant device support can be tested.

Expand Down
Loading