Xseventh commented on issue #362:
URL: https://github.com/apache/tvm-ffi/issues/362#issuecomment-3691649119

   > `@tvm_ffi.dataclasses.c_class` is currently highly experimental and that's 
why they are not part of our public APIs: 
https://tvm.apache.org/ffi/reference/python/index.html.
   > 
   > If you are looking for well-tested stable APIs, 
[`tvm_ffi.register_object`](https://tvm.apache.org/ffi/reference/python/generated/tvm_ffi.register_object.html)
 is likely the go-to option. We have a tutorial regarding registering a C++ 
class and expose it to Python: 
https://tvm.apache.org/ffi/packaging/python_packaging.html
   > 
   > * APIs to register C++ class, expose in Python: 
https://tvm.apache.org/ffi/packaging/python_packaging.html#class
   > * A automatic tool that generates field/method: 
https://tvm.apache.org/ffi/packaging/python_packaging.html#stub-generation-tool
   
   I understand that dataclasses.c_class is currently experimental and not part 
of the public API.
   
   I have one question about roadmap and one about what you’d recommend in my 
case:
   
   Do you have a rough roadmap / intended direction for 
tvm_ffi.dataclasses.c_class? Is the goal for it to eventually become a 
supported/stable public API, or is it expected to remain experimental?
   
   In my project I don’t want to use code generation (e.g. stubgen generating 
Python source files). I prefer a runtime / reflection-driven approach that 
materializes Python proxy classes dynamically. In that scenario, would you 
recommend using c_class, or should I instead build on the stable 
register_object API and implement my own thin runtime “class materialization” 
layer?
   
   Thanks!


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to