Skip to content

Commit f4c8c7f

Browse files
authored
Remove obsolete TODOs (#314)
1 parent e471e8a commit f4c8c7f

File tree

1 file changed

+1
-19
lines changed

1 file changed

+1
-19
lines changed

spec/purpose_and_scope.md

+1-19
Original file line numberDiff line numberDiff line change
@@ -48,14 +48,6 @@ functionality that's not present in this document?_ This:
4848
- may indicate that that functionality, if present in a particular array
4949
library, is unlikely to be present in all other libraries
5050

51-
```{note}
52-
53-
This document is ready for wider community review, but still contains a
54-
number of TODOs, and is expected to change and evolve before a first
55-
official release. See {ref}`future-API-evolution` for proposed
56-
versioning.
57-
```
58-
5951
### History
6052

6153
The first library for numerical and scientific computing in Python was
@@ -117,8 +109,7 @@ Furthermore, meta-topics included in this standard include:
117109
- Verification of API standard conformance
118110

119111
The concrete set of functionality that is in scope for this version of the
120-
standard is shown in this diagram (_TODO: update after deciding on how optional
121-
extensions are dealt with_):
112+
standard is shown in this diagram:
122113

123114
![Scope of array API](_static/images/scope_of_array_API.png)
124115

@@ -217,15 +208,6 @@ extensions are dealt with_):
217208
used is best left to the end user._
218209

219210

220-
### TBD whether or not in scope, or for a later version
221-
222-
- Random number generation, Fourier transforms, and miscellaneous functionality
223-
like a padding function.
224-
225-
_This will be decided later, depending on whether "optional extensions" will
226-
be added to the standard._
227-
228-
229211
### Implications of in/out of scope
230212

231213
If something is out of scope and therefore will not be part of (the current

0 commit comments

Comments
 (0)