[jira] [Resolved] (LOG4J2-2768) LogBuilder multi-parameter overloads

["Ralph Goers (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers resolved LOG4J2-2768.
---------------------------------
    Fix Version/s: 2.13.1
       Resolution: Fixed

Patch applied. Please verify and close.

> LogBuilder multi-parameter overloads
> ------------------------------------
>
>                 Key: LOG4J2-2768
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2768
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 2.13.0
>            Reporter: Marius Volkhart
>            Assignee: Ralph Goers
>            Priority: Minor
>             Fix For: 2.13.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The new {{LogBuilder}} interface provides a single {{log(String format, Object... params)}} method for creating formatted messages from a {{String}}. The {{Logger}} methods {{info}}, {{debug}}, etc all had overloads like {{debug(String format, Object p0)}}, {{debug(String format, Object p0, Object p1)}}, etc. This avoided allocating an {{Object[]}} before knowing whether or not the message is going to be logged.
> Were these overloads intentionally omitted from the {{LogBuilder}} API? Is there a new/better way to avoid the {{Object[]}} allocation, or do newer JVMs perhaps not require this anymore? 
> If not, I'd like to request the overloads be added to the {{LogBuilder}} API, and would be happy to submit a PR to do so.
> Google's Flogger has a write up that covers this topic in a bit more detail: https://google.github.io/flogger/anatomy



--
This message was sent by Atlassian Jira
(v8.3.4#803005)