Detect suppliers passed as `Object` parameters about logging-log4j2 HOT 2 CLOSED

I do not believe this is practically solvable using the standard API. However, I propose we enhance the LogBuilder to support this so you would code:

log.atInfo().withArg(() -> quick).withArg(() -> brown).withArg("fox").withArg(() -> "lazy dog").log("The {} {} {} jumps over the {}.");

We could also do

log.atInfo().withMsg("The {} {} {} jumps over the {}.").withArg(() -> quick).withArg(() -> brown).withArg("fox").withArg(() -> "lazy dog").log();

Note that this would have a few implications:

1. withMsg could appear anywhere in the sequence of calls.
2. A second withMsg would replace a prior one.
3. Specifying a message in the log call would replace any messages provided via a withMsg (i.e. - last one wins).
4. The order of the withArg calls matters as they match the order of placeholders.
5. If args are specified in the log call they would be added to the list of args specified (not replace them as the message does).

from logging-log4j2.

I have to agree, I initially thought that we can call Supplier#get() on each parameter that implements Supplier. However in doing so we prevent users from logging objects that accidentally also implement Supplier, e.g. a factory might implement Supplier, but the user might want to log the factory's name instead.

from logging-log4j2.