In our library we have two kinds of debug logs:
- the ones that are printed very often and thus they usually introduce significant overhead and are hard to reason about, but sometimes they’re useful
- the ones that are not printed that often but still can pollute the output in some cases
I’d like to distinguish them and be able to configure whether they should be printed or not. If possible, the silenced ones should be purged at the compile.
I know the logger can be configured to purge logs from particular modules and functions, and while it’s a nice possibility that I’d like to leave available, I think it’s not a good idea to require the lib users to explicitly list all the functions from either category.