How should lazy actx.compile interact with memoization (on the output end)? #100

This is a longer-shot companion issue to https://github.com/inducer/pytato/issues/164 (and #99).

Suppose an actx.compiled function evaluates something that's memoized (for the sake of argument, imagine a temperature in mirgecom). After the compiled evaluation concludes, the memoization of dependent data becomes unavailable, since we're now working on a different array (/array container) instance. It'd be nice if that weren't the case.

(This isn't immensely relevant for mirgecom, since the output of the compiled function will typically be fed into a time integrator, which would invalidate any memoized temperature anyhow.)

cc @kaushikcfd