10000 Add linear algebra design principles by kgryte · Pull Request #149 · data-apis/array-api · GitHub
[go: up one dir, main page]
Skip to content

Add linear algebra design principles #149

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.

Sign up for GitHub

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

Merged
merged 5 commits into from
May 12, 2021
Merged

Add linear algebra design principles #149

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
228369a
Add design principles
kgryte Mar 25, 2021
1837804
Fix grammar
kgryte Mar 25, 2021
3d4e86c
Add additional principle and note regarding namespaces
kgryte Mar 25, 2021
1a0844d
Merge branch 'main' of https://github.com/pydata-apis/array-api into …
kgryte May 12, 2021
db48d9e
Remove note
kgryte May 12, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Remove note
  • Loading branch information
@kgryte
kgryte committed May 12, 2021
commit db48d9e058f137fbad0abccfdfdb2d0854d2d724
7 changes: 0 additions & 7 deletions spec/API_specification/linear_algebra_functions.md
7CF7
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,13 +72,6 @@ Accordingly, the standardization process affords the opportunity to reduce inter

## Objects in API

```{note}

Historically, linear algebra functionality has been split across interfaces belonging to different namespaces. For example, NumPy exposes linear algebra interfaces in both its top-level namespace and its `linalg` sub-namespace. The determination of which linear algebra interface belongs to which namespace is often unintuitive and a common source of confusion.

As this specification has both the benefit of hindsight and the ability to ensure unique identifiers for each interface in an intentionally limited top-level namespace, the need for a dedicated `linalg` sub-namespace is less necessary and has been avoided here.
```

<!-- NOTE: please keep the functions in alphabetical order -->

(function-linalg-cholesky)=
Expand Down
0