## Current issue
TVM current has two different hybrid scripts: `te.hybrid.script` and `tvm.hybrid.script`. This leads to confusion as both scripts are similar but share different use cases and properties. This is especially confusing for new users as hybrid script can refer to either of these names. (I have had discussions with people where we were both referring to different hybrid scripts.) I propose we rename `tvm.hybrid.script` as it is going to be used a lot in the future and is newer than `te.hybrid.script`. I have a couple of possible new names. - tir.script: this name reflects the current use of `tvm.hybrid.script` as a sugar for TIR. - tvm.script: this is a similar name to torch's torchscript. Although `tvm.hybrid.script` supports only TIR right now, in the future we would like it to support relay. This generic name covers this use case. - tvm.script.tir and tvm.script.relay: like tvm.script, but we make the difference between script supporting TIR and script supporting Relay. In the future this may cause an issue if we have a unified script for TIR and Relay (which is a goal of `tvm.hybrid.script`). Personally I am leaning towards tvm.script as I think it will make the most sense to new users and communicates the end goals we have. Which options does everyone like? If you don't like any of these, could you propose a new name? ## Disadvantages Name changing is churn, and can make old docs/discuss posts out of date. But right now there is not that much usage of `tvm.hybrid.script`. Renaming it earlier instead of later will cause fewer issues. We can also mark the `tvm.hybrid.script` identifier as deprecated to allow users time to switch over to the new naming scheme. The initial `tvm.hybrid.script` PR: https://discuss.tvm.apache.org/t/rfc-hybrid-script-support-for-tir/7516 --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-rename-hybrid-script/7915/1) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/d86c56a60a43d080a9088d34bb2b26d3fcbd34cc7f6051e90e7383162998d611).
