Comment 1:

Go does not have the C++ features that the Google logging package needs to provide the
functionality you ask for.  No macros, for one thing.  More generally, there is no way
to provide logging levels efficiently, since the arguments would always be evaluated
even if the logging call is not going to produce any output.
Because these features cannot be provided well, they will not be provided at all. There
are external implementations of logging that are prepared to make the compromise
differently; perhaps they can help you.

Status changed to WontFix.

Comment 2 by awreece:

As I understand, the Google C++ logging package evaluates the arguments whether or not
they produce any output (for example, I know it evaluates the parameters of CHECK  and
LOG expressions but I do not know whether or not the streamed values are evaluated in
the case the CHECK or LOG would produce not output). If this "excessive" evaluation of
parameters is really an issue, then I understand the exclusion from the Go libraries
(although I would be interested in hearing the motivation behind this claim, especially
with regards to the motivation for making the default logging for the C++ library always
evaluate its parameters).
Is it just the issue of evaluating arguments? There appears to be the additional claim
that Go, lacking macros and a preprocessor, cannot support a clean logging package.

Comment 3:

The mailing list is a better place for open-ended discussions
like this one.  VLOG, LOG_IF, DCHECK, and so on definitely
do not evaluate their arguments when disabled.
Russ

Comment 4:

See package log for a clean logging package.
Russ