[
https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14663208#comment-14663208
]
Remko Popma commented on LOG4J2-599:
------------------------------------
Based on the above feedback I will make the following changes:
* Rename LambdaLogger to Logger2
* Rename LogManager#getLambdaLogger methods to getLogger2
* Introduce a custom interface {{org.apache.logging.log4j.util.Supplier<T>}} to
replace the Callable argument
* Introduce a custom interface
{{org.apache.logging.log4j.util.MessageSupplier}} and add methods that mirror
the current {{log(Message)}} methods. (Java's erasure of generics makes it
impossible for the compiler to distinguish between Supplier<Message> arguments
(which can be used as is) and Supplier<String> arguments (which still need to
be wrapped in a message).)
I will first make these changes to the branch. Are we are agreeing enough on
the general approach to merge this into master?
> Support lambda functions (or similar) for log message parameters
> ----------------------------------------------------------------
>
> Key: LOG4J2-599
> URL: https://issues.apache.org/jira/browse/LOG4J2-599
> Project: Log4j 2
> Issue Type: Brainstorming
> Components: Core
> Reporter: Matt Sicker
> Assignee: Remko Popma
> Priority: Minor
> Labels: Java8
>
> It would be nice if we could support 0-param lambda functions (or the
> equivalent: interfaces with a single empty-parameter message call), or more
> simply, allow Runnables (or something similar) to be passed which will be
> dynamically executed if the log message is enabled.
> The use case here is that although string construction of the log message is
> a performance issue that is already solved quite well, the problem of adding
> in information to the log message that makes other calculations still needs
> to be wrapped in an if check.
> I'm not sure if it'd be best to just use Runnable, or create a new interface,
> or try to emulate how Java 1.8 lambdas work via an interface with a single
> method defined. The details here would still need to be fleshed out, but I
> think this sort of feature could be rather handy (especially in a Java 1.8+
> environment, or in Groovy/Scala/etc.).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
