[ 
https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679422#comment-14679422
 ] 

Remko Popma edited comment on LOG4J2-599 at 8/10/15 12:21 AM:
--------------------------------------------------------------

Gary, why do we need LoggerContext2? The only change I had in mind was removing 
the {{getLogger2}} methods from LogManager and changing the return type of the 
{{getLogger}} methods such that they support both Logger and Logger2 (by using 
the generics as Ralph suggested)...


was (Author: [email protected]):
Gary, why do we need LoggerContext2? I was just thinking to remove the 
{{getLogger2}} methods from LogManager an change the return type of the 
{{getLogger}} methods such that they support both Logger and Logger2 (by using 
the generics as Ralph suggested)...

> 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
>             Fix For: 2.4
>
>
> 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]

Reply via email to