> To incorporate that suggestion, this can be done through say > > * On compilation part, have proper namespace, file or folder structure to > indicate the grouping (that we are looking at embedded rust) so to avoid > confusion with other rust APIs. > * (a) introducing a new namespace; (b) use a particular folder structure that > indicate it is embedded API (c) other possible approaches that helps the > calrifications on the generated API
`interface_c.cc` exists and is not called `interface_embedded_c.cc` or `microtvm/c_interface.cc`, therefore we follow the existing convention to add `interface_rust.cc`. > To be absolutely clear, I did not ask for a change of the embedded C > interface. I do not want to introduce more inconsistency to the TVM codebase by only changing one of the APIs, and we should therefore change both together to whatever is the desired state - which is not in scope of this RFC. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/96#issuecomment-1373402221 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/96/c1373402...@github.com>
