@nikolavojicic it’s a clj feature that is a global dynamic var. it isn’t able to distinguish between your ns’s and those you require while compiling them.

You could probably consider just filtering the warning output perhaps if you wanted less noise. But not built in.

One can put (set! **warn-on-reflection** true) into a single file with one namespace, and it affects only the compilation of that namespace. I do not know exactly how Leiningen treats the value of the :global-vars key, but it apparently by default applies it equally to all files being compiled, somehow.

it's just bound higher in the stack

when you put it in the file it's only on the stack during the load of that file