Hi @jcf94,
[quote="jcf94, post:5, topic:7930"] IMHO, advanced users who may benefit from it are more likely to write their C++ code directly, while other users may not really have a requirement on this. [/quote] First, this is not only for C++ code generation. In the future, we will extend it for Python/Rust code generation, which is helpful for unifying object definitions between different languages. Second, some object fields is hard to fill in even for advanced users, e.g, `type_child_slots`, which is the number of object's children. And last but not least, by defining objects with tschema, we will have more in-memory information about the object itself. For example, the type hierarchy between objects, the memory layout of an object, etc. This will enable more compilation optimization in the TIR and help us improve TIR's type system (my next step). [quote="jcf94, post:5, topic:7930"] Another problem is I guess it will be hard for a IDE or editor(e.g. VSCode, Vim with CTags) to track the code and provide navigation? [/quote] Since we will keep the generated C++ code in the codebase, it will not make any difference with current code in terms of code navigation. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-tvm-object-schema-dsl/7930/7) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/e4d194bd51b13c8cb8ae128ecf02ca1c9b08c8bfd1af12b557b75680d736026b).
