Repository navigation
Loopy a hard dependency? #247
Description
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!
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!
Activity
inducer commentedon Sep 26, 2023
I would be sympathetic to removing it. The one conceivable reason is that
call_loopyis 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 viasingledispatch. As you know, there's precedent (Jax) that doesn't support it.