@@ -144,7 +144,7 @@ standard is shown in this diagram:
144
144
_ Rationale: execution is the domain of implementations. Attempting to specify
145
145
execution behavior in a standard is likely to require much more fine-grained
146
146
coordination between developers of implementations, and hence is likely to
147
- become an obstable to adoption._
147
+ become an obstacle to adoption._
148
148
149
149
3 . Non-Python API standardization (e.g., Cython or NumPy C APIs)
150
150
@@ -153,14 +153,13 @@ standard is shown in this diagram:
153
153
this point in time to standardize anything. See
154
154
the [ C API section] ( design_topics/C_API.md ) for more details._
155
155
156
- 4 . Standardization of these dtypes is out of scope: bfloat16, complex, extended
156
+ 4 . Standardization of these dtypes is out of scope: bfloat16, extended
157
157
precision floating point, datetime, string, object and void dtypes.
158
158
159
159
_ Rationale: these dtypes aren't uniformly supported, and their inclusion at
160
160
this point in time could put a significant implementation burden on
161
161
libraries. It is expected that some of these dtypes - in particular
162
- ` bfloat16 ` , ` complex64 ` , and ` complex128 ` - will be included in a future
163
- version of the standard._
162
+ ` bfloat16 ` - will be included in a future version of the standard._
164
163
165
164
5 . The following topics are out of scope: I/O, polynomials, error handling,
166
165
testing routines, building and packaging related functionality, methods of
0 commit comments