We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
I don't see a mention of this in the documentation.
The logger methods don't take their msg param by-name, but I guess the macro implementations may be providing that "laziness" to the msg-construction.
logger
msg
If I have a complicated interpolated string, I don't want to create it unless I am actually going to log it…
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I don't see a mention of this in the documentation.
The
logger
methods don't take theirmsg
param by-name, but I guess the macro implementations may be providing that "laziness" to the msg-construction.If I have a complicated interpolated string, I don't want to create it unless I am actually going to log it…
The text was updated successfully, but these errors were encountered: