@junrushao1994 ok, just want to clarify one question here: > TVMScript users could write a python/rust code, while it's pretty infeasible > for them to write JSON with bare hand. 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.
i have heard some folks in the community interested in converting TIR to JSON (I think @SebastianBoblestETAS and @MichaelJKlaiber if memory serves), but I also think that the use cases they're interested in could be accomplished if we had a user-friendly, robust Python interface to the TIR. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/74#issuecomment-1159180245 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/74/c1159180...@github.com>
