Evaluate arguments only if they are to be logged #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR proposes that arguments passed as
...
are only evaluated if they are to be logged.Motivation and background
This increases performance if logs on certain levels (e.g.
TRACE
) require non-negligible time to produce. One practical example is logging the hashes of files being read for reconciliation purposes. Currently, if we use:logger::log_trace("md5=", tools::md5sum(filePath))
the
md5sum
will be calculated regardless of the threshold, increasing runtime even if the threshold is lower than that forTRACE
and nothing will be logged.After the change, the arguments would be evaluated only if they really are to be logged and therefore are needed.