Runtime switches for Optick API calls

[curldivergence]

Hello,

I have a question: do I understand correctly that currently we can not enable or disable calls to Optick API's like optick::event! etc. in runtime, so if one wants to disable them, than Cargo features are the only options? If it is so, probably it's worth it for Optick API's to receive some kind of predicate that would define if they are or are not no-ops, so that profiling could be switched on and off in runtime?

Thanks!