search

inducer / arraycontext

Choose your favorite numpy-workalike!
6 stars 11 forks source link

Loopy a hard dependency? #247

Open kaushikcfd opened 1 year ago

kaushikcfd commented 1 year ago

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

Thanks!

inducer commented 1 year ago

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.