tqchen commented on PR #96: URL: https://github.com/apache/tvm-rfcs/pull/96#issuecomment-1373871671
> C is used for a variety of use-cases and is foundational to much of the software used in larger systems (not only embedded) I am not denying that fact. Assembly language can also be used to build up a broader spectrum of systems --just most people don't do that, and normal audiences of tvm don't use things in that way. Most of the developer community that interfaces with tvm through c are from the base that normally interacts with resource constraint settings. Likely a smaller portion of the rust developer commuinty likely will take that view. > which serves the same audience - set A: The set of audiences who would interact with the embedded C API - set B: The set of audiences who would interact with the embedded Rust API - set Ax: The set of audiences who would normally use C language - set Bx: The set of audiences who would normally use Rust language You are stating that set A and set B are the same. Which is of course not wrong. But when we design for the project, we want to not only consider the area of audiences that we are targetting, but also the audiences to the project in general. In our case, set Ax ~ A (most people who uses Ax would also be using or prefer A), as a result there will be less confusion for audiences in Ax. In the case of rust, set Bx is bigger than B. The suggestions are made on that basis not only considering embedded C and rust API, but also general TVM project(and broader tvm community) as a whole for this specific context of rust language in this RFC -- I am only making that statement because the proposed change is not very properly scoped and can affect audiences in Bx that are not in B. Having proper namespacing or calrification is not a strong requirement, since it is not excluding the particular module because of existence of other rust APIs, and also helps to clearly signal the overall the intent helps to empower the community members both in A, B, Ax and Bx. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@tvm.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
