new (and successful :) ) story for 'parent/overridden irtrees'. basically, if we have a rule which maps some eval X's type from A -> B, we preserve the original ir-tree compilation of A in the 'history' when we inevitably produce the ir-tree compilation of B. this can be used for accesses on overridden evaluations, and it allows us to implement $ in auto view rules.

src/eval/eval_ir.h

@@ -152,6 +152,9 @@ struct E_IRState
   // rjf: unpacked ctx
   RDI_Procedure *thread_ip_procedure;
   
+  // rjf: overridden irtree
+  E_IRTreeAndType *overridden_irtree;
+  
   // rjf: caches
   E_UsedExprMap *used_expr_map;
   E_TypeAutoHookCacheMap *type_auto_hook_cache_map;