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
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.
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.
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
https://github.com/inducer/arraycontext/blob/main/setup.py#L46 ↩
The text was updated successfully, but these errors were encountered: