> people use text format for readability, and in most usecases, go for json > reliable serialization.
what do you mean by "reliable" here? if they're truly roundtrippable, aren't they both reliable? just trying to understand :) > Instead, for metaprogramming capability, one may need to interleave host > language-based IRBuilder with the parser. Is the goal then that you'd be able to serialize an IRModule which contains fragments that need to be repeated via meta-programming? then, if you did this using a host language's IRBuilder, you could quickly write some meta-programming steps in that host language to expand the program. >To clarify, TIR is a DSL independent of any existing language. ... Python >syntax is an add-on for usability but TIR design is in no ways matched to >python. I agree with your statement, but I thought the repr form of TIR wasn't so easy to work with and thus the motivation for TVMScript. While I agree that TIR is technically separate, if TVMScript is a core way in which TIR is used, I'd argue we should treat them conceptually as joined (e.g. TVMScript as the recommended roundtrip text format for TIR). What are your thoughts there? -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/74#issuecomment-1151765150 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/74/c1151765...@github.com>
