Thanks, I think this will be very useful. I think the benefit of this approach is that it allows the run-time to be customized much more easily. I like the idea of being able to cache an *engine* (in my case this will be a series of ACL functions) - this opens up opportunity for optimization of libraries that are stateful and therefore reduce overhead on subsequent runs of the same module. It looks like this will generalize much of what I have in my current `ACLRuntimeModule` implementation.
Just some questions I have, mostly relating to problems I ran into with my current implementation... I may be pushing the idea behind this RFC slightly: * Is there any plan to include a generic JSON graph representation which can be traversed in the runtime or will this be upto the library integrator? I can see many libraries implementing similar representations. * How do you plan on serializing params i.e. *base64 serialized ndarray*? Or will this again be left to the integrator to decide? --- [Visit Topic](https://discuss.tvm.ai/t/byoc-runtime-json-runtime-for-byoc/6579/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/46ef95ef09dc8c4bddca7a554b2d71c071149ed6b3fcd776917ad2627596fc3f).
