> Relay has a single roundtrippable serialization format, as do most languages. > I think we benefit from this in that we only have one set of tests to > maintain.
To clarify, Relay has two roundtrippable serialization formats: text format and json. people use text format for readability, and in most usecases, go for json reliable serialization. > why we want to have two ways to parse TVMScript First of all, the RFC focuses on the printer, so would be great if we talk about the parser in the incoming RFC, but to clarify, we are not having two ways to parse TVMScript in the same language. Instead, for metaprogramming capability, one may need to interleave host language-based IRBuilder with the parser. > language constructs in TIR somewhat closely matched to Python. To clarify, TIR is a DSL independent of any existing language. It's somewhat close to HalideIR but has been evolving for years with lots of new features, for example, blocks. Python syntax is an add-on for usability but TIR design is in no ways matched to python. Anyways, I'm happy to talk more on the upcoming metaprogramming RFC. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/74#issuecomment-1150681679 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/74/c1150681...@github.com>
