@tqchen, yeah those are good points. One possibility would be to use hand-written languages for first-tier-supported languages like python and offer the auto-generated wrappers for other languages.
If you did end up switching fully to auto-generated wrappers you could take steps like committing generated code to the git repo to make it easier to browse, with doc comments leading back to the original source code. Ultimately, though, it'll always be less natural than hand-written wrappers, that's definitely true. RE: the Node heirarchy, it seems like doing more with that is an unambiguous win. I could imagine setting up a system like the `TVM_REGISTER_GLOBAL` macro + maybe macros for declaring attributes so that you don't have to hand-code visitAttrs. Did you have other thoughts on that design? -- 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/2983#issuecomment-480657099
