hmm, then does it make sense to have a another derived class, say `MemoizedExprFunctor`, that does have a memo logic built in, for a simple use case in derived classes that requires memoization? The PR I saw today could derive from this instead of ExprFunctor, for example.
Basically for encapsulating already duplicated logics in our codebase. The rest of code that needs more care are not going to be affected. --- [Visit Topic](https://discuss.tvm.ai/t/missing-memoization-in-exprfunctor/6334/3) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/81affa1ec89201499c28a39a143dfd3f9b88261fa0c652e4dcf1938a4e3c72a2).
