> It will however, come with benefit of clarity for broader TVM communty > members who are interested in Bx but not in B, or both in (Bx-B) and B. As a > result the requested change, which i believe would be net positive for > developer users both in (Bx - B) and B. They are pretty actionable with > reasonings that listed above.
We should make it clear for a C developer to choose the larger dynamic or the dinkier embedded variant of the API in the same way we should make it clear for a Rust developer. I am not going to introduce inconsistencies in how we treat embedded interfaces for languages that support embedded environments as part of this RFC. If this is unacceptable I will consider this RFC rejected and close it. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/96#issuecomment-1375907195 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/96/c1375907...@github.com>
