from a quick grepping it seems that the log macro does not extract the file and line from the callsite.
Such info would seem 1) just data, just like any other (and therefore cheap, in an "open world" following Clojure's philosophy) and 2) an overall useful piece of information that can accelerate debugging time and/or be integrated with misc tooling (e.g. something like the datadog github integration, which shows your relevant clj source code right next to your data).
I wonder if this is a feature you've considered, and if so, why would it might not be a good idea to capture this info.
Worst-case scenario, I reckon that one could craft his own minimalistic log macro that wrapped mulog's, with an extra μ/with-context being macroexpanded:
Hi Bruno,
from a quick grepping it seems that the
logmacro does not extract the file and line from the callsite.Such info would seem 1) just data, just like any other (and therefore cheap, in an "open world" following Clojure's philosophy) and 2) an overall useful piece of information that can accelerate debugging time and/or be integrated with misc tooling (e.g. something like the datadog github integration, which shows your relevant clj source code right next to your data).
I wonder if this is a feature you've considered, and if so, why would it might not be a good idea to capture this info.
Worst-case scenario, I reckon that one could craft his own minimalistic
logmacro that wrapped mulog's, with an extraμ/with-contextbeing macroexpanded:...However It would be more comfortable to stick to an official API, or at least learn a bit about your thinking.
Cheers - V