Thanks @zackcquic . To follow up on naming,
My understanding is that instrument goes beyond profiling(e.g. can use to collect the IRs being passed around, dump the IR across pass runs for generate debugging purposes). The proposal is essentially a structured form of tracing. Because of that reason, instrument/tracing would be a better namespace than profiling. We can discuss the specific naming convention by looking into the convention used by existing frameworks. If the class overload and instrumentation is more common than functional trace callback, we can go with that route, as long as the naming is consistent. --- [Visit Topic](https://discuss.tvm.apache.org/t/pass-instrument-framework-proposal/9874/5) 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/fb8c64ff48ae9c34c2475c967f4ae26b2c860b65a9768bd2f1d0ca428e2c2928).
