[
https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659216#comment-14659216
]
Remko Popma edited comment on LOG4J2-599 at 8/6/15 12:20 AM:
-------------------------------------------------------------
I agree there is no need to hold up the release for this. On the other hand I
don't want to suspend discussing things or suspend working on features. If it
makes the cut, fine, if not, that is fine too.
To continue the discussion, would this API change require us to change our
version number to 3.0? To clarify, I am not in favor of this. One reason is
that I can't imagine this change would break anyone's client code. Another
consideration is that to me the 3.0 number suggests a major architectural
change, while this is actually a fairly minor code change.
was (Author: [email protected]):
I agree there is no need to hold up the release for this. On the other hand I
don't want to suspend discussing things or suspend working on features. If it
makes the cut, fine, if not, that is fine too.
To continue the discussion, would this API change require us to change our
version number to 3.0?
> 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
> 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]
