Deploy: 95332bb

Author: array-api-bot

2022.12/API_specification/array_object.html

@@ -712,7 +712,8 @@ <h3 id="comparison-operators">Comparison Operators<a class="headerlink" href="#c
 </ul>
 </li>
 </ul>
-<p>Comparison operators should be defined for arrays having any data type.</p>
+<p><a class="reference internal" href="generated/array_api.array.__lt__.html#array_api.array.__lt__" title="array_api.array.__lt__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__lt__()</span></code></a>, <a class="reference internal" href="generated/array_api.array.__le__.html#array_api.array.__le__" title="array_api.array.__le__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__le__()</span></code></a>, <a class="reference internal" href="generated/array_api.array.__gt__.html#array_api.array.__gt__" title="array_api.array.__gt__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__gt__()</span></code></a>, <a class="reference internal" href="generated/array_api.array.__ge__.html#array_api.array.__ge__" title="array_api.array.__ge__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__ge__()</span></code></a> are only defined for arrays having real-valued data types. Other comparison operators should be defined for arrays having any data type.
+For backward compatibility, conforming implementations may support complex numbers; however, inequality comparison of complex numbers is unspecified and thus implementation-dependent (see <a class="reference internal" href="../design_topics/complex_numbers.html#complex-number-ordering"><span class="std std-ref">Complex Number Ordering</span></a>).</p>
 </section>
 <section id="in-place-operators">
 <h3 id="in-place-operators">In-place Operators<a class="headerlink" href="#in-place-operators" title="Permalink to this heading">¶</a></h3>

2022.12/_sources/API_specification/array_object.rst.txt

@@ -163,7 +163,8 @@ A conforming implementation of the array API standard must provide and support a
     -   `operator.ne(x1, x2) <https://docs.python.org/3/library/operator.html#operator.ne>`_
     -   `operator.__ne__(x1, x2) <https://docs.python.org/3/library/operator.html#operator.__ne__>`_
 
-Comparison operators should be defined for arrays having any data type.
+:meth:`.array.__lt__`, :meth:`.array.__le__`, :meth:`.array.__gt__`, :meth:`.array.__ge__` are only defined for arrays having real-valued data types. Other comparison operators should be defined for arrays having any data type.
+For backward compatibility, conforming implementations may support complex numbers; however, inequality comparison of complex numbers is unspecified and thus implementation-dependent (see :ref:`complex-number-ordering`).
 
 In-place Operators
 ~~~~~~~~~~~~~~~~~~

2022.12/searchindex.js

@@ -712,7 +712,8 @@ <h3 id="comparison-operators">Comparison Operators<a class="headerlink" href="#c
 </ul>
 </li>
 </ul>
-<p>Comparison operators should be defined for arrays having any data type.</p>
+<p><a class="reference internal" href="generated/array_api.array.__lt__.html#array_api.array.__lt__" title="array_api.array.__lt__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__lt__()</span></code></a>, <a class="reference internal" href="generated/array_api.array.__le__.html#array_api.array.__le__" title="array_api.array.__le__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__le__()</span></code></a>, <a class="reference internal" href="generated/array_api.array.__gt__.html#array_api.array.__gt__" title="array_api.array.__gt__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__gt__()</span></code></a>, <a class="reference internal" href="generated/array_api.array.__ge__.html#array_api.array.__ge__" title="array_api.array.__ge__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__ge__()</span></code></a> are only defined for arrays having real-valued data types. Other comparison operators should be defined for arrays having any data type.
+For backward compatibility, conforming implementations may support complex numbers; however, inequality comparison of complex numbers is unspecified and thus implementation-dependent (see <a class="reference internal" href="../design_topics/complex_numbers.html#complex-number-ordering"><span class="std std-ref">Complex Number Ordering</span></a>).</p>
 </section>
 <section id="in-place-operators">
 <h3 id="in-place-operators">In-place Operators<a class="headerlink" href="#in-place-operators" title="Permalink to this heading">¶</a></h3>

draft/API_specification/array_object.html

@@ -163,7 +163,8 @@ A conforming implementation of the array API standard must provide and support a
     -   `operator.ne(x1, x2) <https://docs.python.org/3/library/operator.html#operator.ne>`_
     -   `operator.__ne__(x1, x2) <https://docs.python.org/3/library/operator.html#operator.__ne__>`_
 
-Comparison operators should be defined for arrays having any data type.
+:meth:`.array.__lt__`, :meth:`.array.__le__`, :meth:`.array.__gt__`, :meth:`.array.__ge__` are only defined for arrays having real-valued data types. Other comparison operators should be defined for arrays having any data type.
+For backward compatibility, conforming implementations may support complex numbers; however, inequality comparison of complex numbers is unspecified and thus implementation-dependent (see :ref:`complex-number-ordering`).
 
 In-place Operators
 ~~~~~~~~~~~~~~~~~~

draft/_sources/API_specification/array_object.rst.txt

@@ -712,7 +712,8 @@ <h3 id="comparison-operators">Comparison Operators<a class="headerlink" href="#c
 </ul>
 </li>
 </ul>
-<p>Comparison operators should be defined for arrays having any data type.</p>
+<p><a class="reference internal" href="generated/array_api.array.__lt__.html#array_api.array.__lt__" title="array_api.array.__lt__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__lt__()</span></code></a>, <a class="reference internal" href="generated/array_api.array.__le__.html#array_api.array.__le__" title="array_api.array.__le__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__le__()</span></code></a>, <a class="reference internal" href="generated/array_api.array.__gt__.html#array_api.array.__gt__" title="array_api.array.__gt__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__gt__()</span></code></a>, <a class="reference internal" href="generated/array_api.array.__ge__.html#array_api.array.__ge__" title="array_api.array.__ge__"><code class="xref py py-meth docutils literal notranslate"><span class="pre">array.__ge__()</span></code></a> are only defined for arrays having real-valued data types. Other comparison operators should be defined for arrays having any data type.
+For backward compatibility, conforming implementations may support complex numbers; however, inequality comparison of complex numbers is unspecified and thus implementation-dependent (see <a class="reference internal" href="../design_topics/complex_numbers.html#complex-number-ordering"><span class="std std-ref">Complex Number Ordering</span></a>).</p>
 </section>
 <section id="in-place-operators">
 <h3 id="in-place-operators">In-place Operators<a class="headerlink" href="#in-place-operators" title="Permalink to this heading">¶</a></h3>

draft/searchindex.js

@@ -163,7 +163,8 @@ A conforming implementation of the array API standard must provide and support a
     -   `operator.ne(x1, x2) <https://docs.python.org/3/library/operator.html#operator.ne>`_
     -   `operator.__ne__(x1, x2) <https://docs.python.org/3/library/operator.html#operator.__ne__>`_
 
-Comparison operators should be defined for arrays having any data type.
+:meth:`.array.__lt__`, :meth:`.array.__le__`, :meth:`.array.__gt__`, :meth:`.array.__ge__` are only defined for arrays having real-valued data types. Other comparison operators should be defined for arrays having any data type.
+For backward compatibility, conforming implementations may support complex numbers; however, inequality comparison of complex numbers is unspecified and thus implementation-dependent (see :ref:`complex-number-ordering`).
 
 In-place Operators
 ~~~~~~~~~~~~~~~~~~