You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently above results in log category auto-naming making the log category
of package.foobar.call-with-wrapping.lambda, which is too much information we don't want.
Its possible to fix the above pattern, by adding a logger object argument to call-with-wrapping, and passing the logger object to macro like this.
But it would be nice if above can be done without such workaround, by adding some syntax sugar to logging macros, that indicate that auto category naming should drop a level, something like (log:trace /// ....) or (log:trace ***) to indicate that naming should drop 3 levels
The text was updated successfully, but these errors were encountered:
There is an often used pattern is Lisp for writing wrappers like this:
Currently above results in log category auto-naming making the log category
of
package.foobar.call-with-wrapping.lambda
, which is too much information we don't want.Its possible to fix the above pattern, by adding a logger object argument to call-with-wrapping, and passing the logger object to macro like this.
But it would be nice if above can be done without such workaround, by adding some syntax sugar to logging macros, that indicate that auto category naming should drop a level, something like
(log:trace /// ....)
or(log:trace ***)
to indicate that naming should drop 3 levelsThe text was updated successfully, but these errors were encountered: