You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, enp implements custom code to support JAX, PyTorch, and TensorFlow.
The array-api-compat library provides a uniform API for numerical computation across multiple frameworks. By leveraging this library, we could potentially:
Eliminate the need for custom code handling framework-specific functionalities.
Simplify updates and bug fixes by relying on a standardized API.
Ensure uniform behavior across different frameworks.
Integrating array-api-compat would not only streamline the codebase but also broaden the number of frameworks compatible with enp. I'm happy to discuss this further and potentially contribute to the implementation if the maintainers agree this is a worthwhile enhancement. Please share your thoughts and suggestions on this proposal.
The text was updated successfully, but these errors were encountered:
I can set aside some time to create a draft in the coming weeks. About TensorFlow, I'm not quite sure why array-api-compat doesn't fully support it yet.
Currently,
enp
implements custom code to support JAX, PyTorch, and TensorFlow.The
array-api-compat
library provides a uniform API for numerical computation across multiple frameworks. By leveraging this library, we could potentially:I propose exploring the feasibility of integrating
array-api-compat
as a backend forenp
. This might involve refactoring existing code to utilize the library's API. Popular libraries like scikit-learn (https://labs.quansight.org/blog/array-api-support-scikit-learn) and SciPy (https://labs.quansight.org/blog/scipy-array-api) have already successfully implemented this API.Integrating
array-api-compat
would not only streamline the codebase but also broaden the number of frameworks compatible withenp
. I'm happy to discuss this further and potentially contribute to the implementation if the maintainers agree this is a worthwhile enhancement. Please share your thoughts and suggestions on this proposal.The text was updated successfully, but these errors were encountered: