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.

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

Jump to bottom

Introduce "@not_supported" decorator #456

Open
guilhermeleobas opened this issue Mar 17, 2022 · 0 comments
Open

Introduce "@not_supported" decorator #456

guilhermeleobas opened this issue Mar 17, 2022 · 0 comments
Labels
documentation Document a feature enhancement New feature or request

Comments

@guilhermeleobas
Copy link
Contributor

From #453 (review)

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Document a feature enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@guilhermeleobas