> 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 as they start to interact with the APIs. > > For example, putting some of the API under `micro` namespace(actually any > namespace that the community might prefer) 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.
I'm not disagreeing with the sentiment, I'm suggesting it's out of scope within this RFC which enables the Embedded API in Rust alongside C. If we want to make changes which impact both the existing Embedded C Interface and the Embedded Rust Interface, I'd suggest we do that in a separate RFC which we can consider both rather than inflating the scope of this RFC to encompass all Embedded Interfaces. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/96#issuecomment-1372661932 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/96/c1372661...@github.com>
