David Beaumont

Tip (in case it wasn't clear in the docs): You really want to be setting up the logger in a **private static final** field in the class rather than doing...

The hot-spot compiler is good at folding stuff like that into efficient code. CPU is cheap compared to allocations and GC pressure. Yes, there are 2 (or more) calls to...

Oh yes, we certainly have, at least inside Google. After a week of attempting to pull out any reliable measure of the potential overhead, I gave up. Under realistic conditions...

> As I mentioned I have implemented a logging API. I didn't say it was necessary, I said I preferred it. You could always create your own singleton LogFactory or...

First things first: To build the entire project, "bazel build //..." should work from the top level directory. As for "Tags", perhaps the name isn't perfect, but that's not changing...

Actually it's even easier that I suggest above since I wrote a helper class for builder metadata handlers. https://github.com/google/flogger/blob/master/api/src/main/java/com/google/common/flogger/backend/MetadataKeyValueHandlers.java#L82 An example of what you might implement: ```java /** A handler...

The right way to fix this is to open-source the customizable message formatter we currently use internally. This allows more customization than just changing the suffix/prefix.

I'm afraid the SLF4J backend was a community contributed backend and isn't supported directly by Google. If you want to dig into the code and look for a solution I...

""If the configured SLF4J back-end supports configuration of call-site resolution it should be setup to grab callers of com.google.common.flogger.FluentLogger#forEnclosingClass (or your custom Flogger logger class, if any)."" That's probably not...

I'll personally not work on this (no time) but I will see about looking into the Log4j2 issue and see if that's easy enough.