Skip to content
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

Add unimplemented functions from array_api #453

Conversation

guilhermeleobas
Copy link
Contributor

This doesn't implement all the functions, only include the files so that they can show up in the docs.

@guilhermeleobas guilhermeleobas added enhancement New feature or request documentation Document a feature labels Mar 15, 2022
@guilhermeleobas guilhermeleobas self-assigned this Mar 15, 2022
@guilhermeleobas guilhermeleobas requested review from tupui and pearu March 15, 2022 03:16
@guilhermeleobas guilhermeleobas marked this pull request as ready for review March 15, 2022 03:16
Copy link
Contributor

@tupui tupui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok so the goal is to have the full Array API defined but raise if something is not implemented. Sounds good.

rbc/stdlib/array_methods.py Outdated Show resolved Hide resolved
rbc/stdlib/array_attributes.py Outdated Show resolved Hide resolved
@guilhermeleobas guilhermeleobas force-pushed the guilhermeleobas/missing_array_api_funcs branch from 48abb56 to 99068f2 Compare March 15, 2022 22:09
@guilhermeleobas guilhermeleobas force-pushed the guilhermeleobas/missing_array_api_funcs branch from 99068f2 to 3cd9c85 Compare March 15, 2022 22:11
Copy link
Contributor

@tupui tupui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@pearu pearu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have only a few comments, otherwise looks good.

While implementing and documenting Array API in the HeavyDB context, I think we should clearly distinguish the "Not implemented" and "Not supported" cases. The "not implemented" means that the corresponding feature can be implemented if taken some time for it, while "not supported" means that the corresponding feature does not makes sense because the underlying datastructures do not support it. For instance, OmnisciDB currently is able to support only 1-D arrays, and hence, we should not give hope to users that inherently N-D operations such as matrix operations can be supported via raising an rbc issue.

rbc/omnisci_backend/omnisci_array.py Outdated Show resolved Hide resolved
rbc/omnisci_backend/omnisci_array.py Outdated Show resolved Hide resolved
rbc/omnisci_backend/omnisci_array.py Outdated Show resolved Hide resolved
Copy link
Contributor

@pearu pearu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks, @guilhermeleobas !

@guilhermeleobas guilhermeleobas merged commit c84a11a into heavyai:master Mar 17, 2022
@guilhermeleobas guilhermeleobas deleted the guilhermeleobas/missing_array_api_funcs branch March 17, 2022 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Document a feature enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants