Skip to content

Commit

Permalink
Clarify expected behavior when providing a complex number array to `a…
Browse files Browse the repository at this point in the history
…ll` and `any` (#442)
  • Loading branch information
kgryte authored Jun 6, 2022
1 parent 5ba86db commit 7ee81a5
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions spec/API_specification/array_api/utility_functions.py
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@ def all(x: array, /, *, axis: Optional[Union[int, Tuple[int, ...]]] = None, keep
.. note::
Positive infinity, negative infinity, and NaN must evaluate to ``True``.
.. note::
If ``x`` has a complex floating-point data type, elements having a non-zero component (real or imaginary) must evaluate to ``True``.
.. note::
If ``x`` is an empty array or the size of the axis (dimension) along which to evaluate elements is zero, the test result must be ``True``.
Expand All @@ -32,6 +35,9 @@ def any(x: array, /, *, axis: Optional[Union[int, Tuple[int, ...]]] = None, keep
.. note::
Positive infinity, negative infinity, and NaN must evaluate to ``True``.
.. note::
If ``x`` has a complex floating-point data type, elements having a non-zero component (real or imaginary) must evaluate to ``True``.
.. note::
If ``x`` is an empty array or the size of the axis (dimension) along which to evaluate elements is zero, the test result must be ``False``.
Expand Down

0 comments on commit 7ee81a5

Please sign in to comment.