[
https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679563#comment-14679563
]
Remko Popma commented on LOG4J2-599:
------------------------------------
Yes, bank/securities firm, doing algorithmic trading systems design and
development. Lots of rules and regulations... :-|
I'll take a look at the text later tonight. Thanks for removing the Logger2
references!
About {{entry(Object...)}}, the intention is that parameters are passed in as
is (no expensive operation). {{AbstractLogger}} already constructs the Message
lazily after checking TRACE is enabled and the ENTRY marker is enabled so I
didn't think an {{entry(Supplier<?>...)}} was necessary. Did I miss something?
Finally, I would prefer to keep the utility class name {{LambdaUtil}}; I like
names that reflect the intention rather than the mechanism that is used to
achieve it. To me "lambda" is more recognizable than "Supplier".
> 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]
