The logging templates in logger reference procs like error, info, warn etc. from the logging module. These are implicitly bound, as they have exactly 1 overload in the scope of the template definitions (https://github.com/nim-lang/Nim/issues/11184).
If this behavior of Nim or the context in logger were to change, these would start preferring procs like macros.error instead and cause issues. Explicitly binding them keeps the current behavior consistent.
An alternative would be to directly call logging.error join(args) etc.
The logging templates in
loggerreference procs likeerror,info,warnetc. from theloggingmodule. These are implicitly bound, as they have exactly 1 overload in the scope of the template definitions (https://github.com/nim-lang/Nim/issues/11184).If this behavior of Nim or the context in
loggerwere to change, these would start preferring procs likemacros.errorinstead and cause issues. Explicitly binding them keeps the current behavior consistent.An alternative would be to directly call
logging.error join(args)etc.