Cool things!
If the initial pattern is with the cast operations, you can then profile and guard an optimized (=static) version of the autocast. In fact, if the fusers incuded the autocast node in their fusion group, this will happen automatically.
For the interop with eager I think we eventually need to dispatch on this in one way or the other. As mentioned on slack, I think we might have a good think whether the issue of having some global (well, or thread) state needing to influence the JIT graph is particular to autocast or whether it’ll show up more.
Best regards
Thomas