Skip to content

Restructure modules #1213

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

Open
ricardoV94 opened this issue Feb 16, 2025 · 0 comments
Open

Restructure modules #1213

ricardoV94 opened this issue Feb 16, 2025 · 0 comments
Labels
Milestone

Comments

@ricardoV94
Copy link
Member

Description

We have very long modules with arbitrary names like tensor.basic vs tensor.extra_ops, and nlinalg vs slinalg. We should organize the modules by operator functionality. I would error on the side of having too many modules than too few. tensor.array_creation, linalg.solve, linalg.decomposition, ..., or even at the level of individual ops when they are complex enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant