cc @jermainewang @kazimuth @junrushao1994 @icemelon9 @ajtulloch @yzhliu who
might be interested in this. Some initial thoughts:
- Convention of the name convention the class and file hierarchy schema
- e.g.``` tvm.schema.expr.py -> include/IR/expr.h```
- Alternatively, allow declaration within each file.
- Decouple schema reading(frontend) and emission, have an IR of class hierarchy
schemas, so that we can have different emitters
- Think about python emitter, c++ emitter
- We might want to use it to also deal with general objects, including
runtime::Object in VM.
- We still want to allow some user-written boilerplate, given that C++
datatypes can still be used in many of those and we would love to have them for
certain internal data types.
- How to handle docstrings
- ATM the python docstrings are separately written, by manual wrapping. The
benefit of manual wrapping is the clear docstrings(as they might be different
from those in c++).
- Should we do the same for now and only generate c++ code?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/dmlc/tvm/issues/3501#issuecomment-508940347
