I think we have all made our points pretty clear. >From technical pov I do not think have clear namespacing or scoping would >bring inconsistency, and if any, that would be more of a minor issue by >looking at the embedded API. They would be significant when looking at the >broader community as a whole due to potential confusion and differences in set >Bx and B. e.g. what if a non-embedded rust developer look at >interface_rust.cc and think how this is related to my way of interacting with >TVM and relation with the existing libtvm rust API.
The suggestion was made by putting the broader TVM community into consideration along with the audiences of the proposal (embedded API users), who are of course also valuable members of the community. That is why the suggestion was made reasonably actionable so will be able continue to emable both the developers in B and (Bx-B). -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/96#issuecomment-1375925390 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/96/c1375925...@github.com>
