-
Notifications
You must be signed in to change notification settings - Fork 52
PR: Add note for functions that are not compatible with static memory allocation #168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 5 commits
Commits
Show all changes
41 commits
Select commit
Hold shift + click to select a range
8815028
Add note for functions that doesn't support boolean array indexing
steff456 2757e73
clarify the notes
steff456 b98c908
remove note from where function
steff456 ad3156d
Some small fixes to function signatures to make them valid Python (#174)
asmeurer e6d827a
Update API specification for creation and manipulation functions (#167)
rgommers b0f4ca0
Change deployment to github actions for github pages (#176)
steff456 0c5d913
Specify the input types for logaddexp (#175)
asmeurer ffc4d0c
Create a unique admonition for data-dependent shapes
rgommers 2e759ef
Add data type guidance (#173)
kgryte 204e283
Rewrite note with the given suggestions
steff456 4d74293
Make axis keyword to squeeze() positional (#100)
rgommers 76730f1
Add Cholesky function specification (#110)
kgryte 059e4fe
Add slogdet specification (#111)
kgryte 9893373
Add specification for computing the pseudo-inverse (linalg: pinv) (#118)
kgryte 36fd440
Add specification for computing the dot product (linalg: vecdot) (#137)
kgryte 0768fc8
Add specification for computing a tensor contraction (linalg: tensord…
kgryte 5677c24
Add linalg solve function specification (#115)
kgryte 56ce784
Add SVD function specification (#114)
kgryte e32a6a8
Add specification for returning the least-squares solution to a linea…
kgryte a33a710
Add specification for computing the qr factorization (#126)
kgryte 3add230
Add specification for computing singular values using singular value …
kgryte fe3b410
Add specification for computing the eigenvalues and eigenvectors of a…
kgryte a1d00d5
Add specification for computing the eigenvalues of a symmetric matrix…
kgryte 7557e69
Add specification for computing the matrix product (linalg: matmul) (…
kgryte e0c0c87
Add specification for computing the number of non-zero singular value…
kgryte 30b0391
Add matrix_power specification (#112)
kgryte d00d255
Fix meshgrid formatting (#178)
leofang 83c6be3
Add linear algebra design principles (#149)
kgryte c2ecccc
Fix matmul formatting (#179)
leofang 9efd284
Fix norm formatting (#181)
leofang 03a2b41
Move linear algebra APIs to an extension (#182)
kgryte 0429693
Fix a typo in the spec (#184)
asmeurer 2472846
Add a requirement for the producer of a DLPack capsule(#186)
leofang e3927fd
Improve documentation for `stream` argument to `__dlpack__` (#185)
rgommers 192b4d7
Clarify that constants are Python scalars (#169)
kgryte 63c592e
Fix typo in definition of __lshift__ (#190)
tomwhite 4c8142c
Merge remote-tracking branch 'steff/add-boolean-indexing-notes' into …
kgryte 0a61b94
Update notes
kgryte c9541aa
Add document stub
kgryte b1fd96e
Add admonition for boolean array indexing and update reference
kgryte 9f336ae
Add explainer on data-dependent output shapes
kgryte File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,6 +15,12 @@ A conforming implementation of the array API standard must provide and support t | |
(function-unique)= | ||
### unique(x, /, *, return_counts=False, return_index=False, return_inverse=False) | ||
|
||
:::{admonition} Data-dependent output shape | ||
:class: important | ||
|
||
The shape of the output array for this function depends on the data values in the input array, hence it can be difficult to implement for libraries that build computation graphs for arrays without knowing their values. See {ref}`indexing` section for more details. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same comment as above. |
||
::: | ||
|
||
Returns the unique elements of an input array `x`. | ||
|
||
#### Parameters | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not clear to me what we are referring to in the "indexing section". I think, instead, what is wanted is to refer to a separate page under "Design topics" where we specifically discuss APIs which return arrays having data-dependent shapes (for further discussion, see here).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we refer to this PR or to the boolean indexing section inside the spec or both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to add a new section in "Design Topics" (via this PR) and then reference that section.