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

Are all combinations of input types really necessary? #30

Open
hameerabbasi opened this issue Oct 22, 2018 · 0 comments
Open

Are all combinations of input types really necessary? #30

hameerabbasi opened this issue Oct 22, 2018 · 0 comments

Comments

@hameerabbasi
Copy link
Contributor

I was wondering whether matching all kinds of input types is really necessary. What NumPy does is it casts the input array to the best supported type, instead of defining kernels for all the types.

This is currently only barely manageable with the current setup... Adding an out= or dtype= may make it exponentially worse, as we have to consider that it may not be the type we expected. Not to mention that mixed types might or might not kill vectorization instructions.

I can't help but wonder if there's a better way to do this, if we can somehow define a set of rules and have the type signatures generated, or if supporting different inputs/outputs is really necessary, or if we can cast to the output dtype as NumPy does.

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

No branches or pull requests

1 participant