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

Loopy a hard dependency? #247

Open
kaushikcfd opened this issue Sep 26, 2023 · 1 comment
Open

Loopy a hard dependency? #247

kaushikcfd opened this issue Sep 26, 2023 · 1 comment

Comments

@kaushikcfd
Copy link
Collaborator

Is there a specific reason why Loopy should be a hard dependency1? My understanding was transform_loopy_program will get kicked in only when the implementation demands.

Thanks!

Footnotes

  1. https://github.com/inducer/arraycontext/blob/main/setup.py#L46

@inducer
Copy link
Owner

inducer commented Sep 26, 2023

I would be sympathetic to removing it. The one conceivable reason is that call_loopy is nominally part of the actx interface, but I think that should be considered an optional part, and it could conceivably be made a function, rather than a method, possibly via singledispatch. As you know, there's precedent (Jax) that doesn't support it.

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

2 participants