@junrushao1994 ah thanks for clarifying! a few follow-ups then: > Imagine you are a rust user who doesn't want to use python, our proposal > makes it possible to develop a frontend in pure rust. And of course, it's not > going to be our priority, i'm just stating the possibility.
Does this mean you can import the JSON-based serialization using only libtvm.so (e.g. rust could import JSON)? If so, then, in the hypothetical prod scenario: >Let's imagine a common usecases in company's prod env where python is strictly >prohibited (e.g. on-device training), but our developers wrote most of the >operators in python, which is the reality. How do we quickly migrate those >operators to C++? , what's the motivation for someone to use IRBuilder instead of just serializing the TVMScript to JSON via parse/print and then ingesting the JSON in their prod env using the JSON parser? > it's not using the design of this proposal and it's totally fine given it's > assuming there are only 2 IRs. Instead, I'm trying to convey is that we build > an open infra for any vendors to integrate with their own IRs, which can be > represented and compiled in the same IRModule with Relax, TIR, etc. That makes sense, thanks for clarifying :) -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/74#issuecomment-1155759976 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/74/c1155759...@github.com>
