Hi @Mousius I think you misunderstood my comments. Perhaps due to the possible confusion "scoping". I am not suggesting to change the interface design or re-define the way to interact with embedded C APIs.
I am only referring to the clarifying the module with proper namespace, folder structure and naming convention helps to bring the clarity to developers and users. For example, putting some of the API under `micro` namespace would help clarifying that the interface was intended for embedded use and works with the micro embedded runtime. That would help the users and developers to differentiate it from say use of libtvm_runtime.so which comes with different set of interface conventions. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/96#issuecomment-1372644643 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/96/c1372644...@github.com>
