tkonolige commented on pull request #6779: URL: https://github.com/apache/incubator-tvm/pull/6779#issuecomment-720644993
It seems like we could cut out a step in the `Object Schema Definition (Python) -> JSON Format Schema (language-agnostic) -> Backend (can be any language like Python or Rust)` process and just do `JSON Format Schema (language-agnostic) -> Backend (can be any language like Python or Rust)`. If we have to do `Python -> JSON -> Python`, what is the point of having the first python? I can understand that writing object definitions in python is a nice user experience, but this isn't a user facing feature (unless I'm missing something?). It just seems like we could avoid all the hassle of manually parsing the python ast (and all the issues that come with it) by using the json format. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
