diff --git a/spec/API_specification/data_types.md b/spec/API_specification/data_types.md
index 61c89d456..76a98638a 100644
--- a/spec/API_specification/data_types.md
+++ b/spec/API_specification/data_types.md
@@ -6,31 +6,11 @@
A conforming implementation of the array API standard must provide and support the following data types.
-```{note}
-
-Data types ("dtypes") are objects that can be used as `dtype` specifiers in functions and methods (e.g., `zeros((2, 3), dtype=float32)`). A conforming implementation may add methods or attributes to data type objects; however, these methods and attributes are not included in this specification.
-```
-
-```{note}
-
-Implementations may provide other ways to specify data types (e.g.,
-`zeros((2, 3), dtype='f4')`); however, these are not included in this specification.
-```
-
-A conforming implementation of the array API standard may provide and support additional data types beyond those described in this specification.
-
-A conforming implementation of the array API standard must define a default floating-point data type (either `float32` or `float64`).
+A conforming implementation of the array API standard must define a default floating-point data type (either `float32` or `float64`), as well as a default data type for an array index (either `int32` or `int64`).
```{note}
-The default floating-point data type should be clearly defined in a conforming library's documentation.
-```
-
-A conforming implementation of the array API standard must define a default data type for an array index (either `int32` or `int64`).
-
-```{note}
-
-The default array index data type should be clearly defined in a conforming library's documentation.
+The default floating-point and array index integer data types should be clearly defined in a conforming library's documentation.
```
@@ -77,3 +57,24 @@ IEEE 754 single-precision (32-bit) binary floating-point number (see IEEE 754-20
## float64
IEEE 754 double-precision (64-bit) binary floating-point number (see IEEE 754-2019).
+
+
+:::{admonition} Future extension
+:class: hint
+It is expected that in the next version of this standard, `complex64` and `complex128`
+dtypes will be added, with these casting rules (will be added to {ref}`type-promotion`):
+
+
+
+See [array-api/issues/102](https://github.com/data-apis/array-api/issues/102)
+for more details.
+:::
+
+```{note}
+Data types ("dtypes") are objects that can be used as `dtype` specifiers in functions and methods (e.g., `zeros((2, 3), dtype=float32)`). A conforming implementation may add methods or attributes to data type objects; however, these methods and attributes are not included in this specification.
+
+Implementations may provide other ways to specify data types (e.g.,
+`zeros((2, 3), dtype='f4')`); however, these are not included in this specification.
+
+A conforming implementation of the array API standard may provide and support additional data types beyond those described in this specification.
+```
diff --git a/spec/_static/images/dtype_promotion_complex.png b/spec/_static/images/dtype_promotion_complex.png
new file mode 100644
index 000000000..3503b07f5
Binary files /dev/null and b/spec/_static/images/dtype_promotion_complex.png differ
diff --git a/spec/conf.py b/spec/conf.py
index 98dd78c5c..308ba52d2 100644
--- a/spec/conf.py
+++ b/spec/conf.py
@@ -50,6 +50,7 @@
# MyST options
myst_heading_anchors = 3
+myst_enable_extensions = ["colon_fence"]
# -- Options for HTML output -------------------------------------------------
pFad - Phonifier reborn
Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.
Alternative Proxies:
Alternative Proxy
pFad Proxy
pFad v3 Proxy
pFad v4 Proxy