Do you have an example of such a macro and the resulting exception trace?
There really isnt much the compiler can do, as it is up to the macro itself to supply source information where it can. Many macros rely on the implicit location information bound to the input of the macro, but more complex macros often should do more but do not necessarily do so.
Consider reporting problems to the macro authors, if you have reproducible cases and a macro generating code that is hard to "trace". Depending on the context it may be possible improve the debugging experience.
As an example: I have some fairly complex macros in a library I wrote and this helper (search for uses of with-loc
) is responsible for transfering the necessary metadata. Without that the errors were much harder to trace back to the actual code. This is for CLJS but the basic method applies to CLJ as well.