Hi! How do you usually use *warn-on-reflection* in code bases for products that you are building? I am discussing this in a code review, where we have used https://github.com/clj-kondo/clj-kondo/blob/master/doc/linters.md#warn-on-reflection to point out files where we do Java interop. For any such file, clj-kondo will say error: Var *warn-on-reflection* is not set in this namespace. if there is no line (set! *warn-on-reflection* true) in that file. And based on those reports, we are now reviewing code where we have inserted a bunch of lines like (set! *warn-on-reflection* true) in different source files that do Java interop. But I am a bit hesitant whether or not it is a good idea to leave these lines in source code. I consider them more of a debugging tool that would usually not be part of the implementation. Instead, I would probably set *warn-on-reflection* for the entire code base from the deps.edn file instead, as suggested in https://stackoverflow.com/a/69790639 . What pros/cons do you see with either approach? That is, sprinkling (set! *warn-on-reflection* true) throughout the code versus having a single setting in deps.edn?