> what functionality does JSON provide that TVMScript doesn't do right now as > it's designed? Is there a reason to have two formats to begin with? imo it is > not worth having two formats here unless there's a clear need for structural > analysis of TIR outside of TVM.
A good analog is the ProtoBuf [text format](https://github.com/protocolbuffers/protobuf/blob/main/src/google/protobuf/text_format.cc) vs. wire format (binary format). People write proto in text format when they need to create proto manually, while the binary format is used in RPC payload for its portability and efficiency. Back to our own use case, TVMScript is the choice if user want to construct IR graph manually, but it's not portable because the TVMScript parser has a strong dependency on Python, especially after the Metaprogramming RFC (#79). On contrast, the JSON format will be portable because it only depends on the IR node definition in C++. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/74#issuecomment-1159471608 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/74/c1159471...@github.com>
