Agreeing with @kparzysz-quic, changes that update the `DLDataType` would need to be approached very cautiously. I usually lean toward allowing short-term breakages if they lead to better long-term code health, but updating the `DLDataType` would be very wide reaching even more my tastes.
One way to limit the scope of the change might be to introduce a distinction between the runtime `DLDataType`, and some new compile-time data-type. This would be analogous to the distinction between the runtime `DLTensor` and the compile-time `tir::Buffer`. It would still involve massive changes inside of TVM, but would preserve the runtime types, avoiding the ABI breakage of compiled functions. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/104#issuecomment-1755890786 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/104/c1755890...@github.com>
